1.0 - Native Shadow Dom vs Shady Dom

[pavelc...@gmail.com]

Shady dom is default in 0.9. This really confuse me. I have some questions. I would really like at last some answered.

Is it true that Native Shadow Dom will be default in 1.0?

What is the reason for Shady being default in 0.9?

Which one is faster? Native use native functions but shady is much lighter.

Should Chrome only website (company IS) be developed in Native Shadow Dom (Polymer = {dom: 'shadow'};)?

Regards, Pavel

[Arthur Evans]

Hi Pavel,

I'll let someone else speak to whether native shadow DOM will be the default in 1.0. I think the reason shady is the default in 0.9 is that it's helpful for testing (both testing the shady DOM code, and ensuring that people get styling that's more consistent with what they'll see on browsers that don't implement shadow DOM natively). 

With 0.5, we saw a lot of people develop on Chrome, and get taken by surprise by styling changes when they tested on another platform.

That said, if you are positive that all of your users are on a browser with native shadow DOM, I'd recommend using native shadow DOM. In my experience it's faster and styling is more accurate. You can also avoid using the Polymer.dom() API for manipulating DOM in this case. (Although that makes it hard to switch to shady should you ever need to support non-shadow DOM browsers.)

Hope this helps,

-Arthur

Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/b386c5f5-4aba-4c90-af94-6ce87f12d265%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[pavelc...@gmail.com]

Thanks Arthur. I will go native :).