Extract inline style block to separate file about grunt-vulcanize HOT 5 CLOSED

The styles need to remain in the Shadow Dom so they're scoped to the
element. Otherwise, it defeats the purpose scoped styles. Under the SD
polyfill, styles are moved to the head, but that's only to shim the styling
features. For native SD they're left in place.
On Apr 3, 2014 2:58 AM, "Pentasis" [email protected] wrote:

Would it be possible and wanted to add an option to extract inline style
blocks and concat them into an external build.css file placed in the HEAD?

Reply to this email directly or view it on GitHubhttps://github.com//issues/3
.

from grunt-vulcanize.

I see. Is this a "limitation" of the polyfill or the spec?

from grunt-vulcanize.

Neither. If you use styles outside of shadow dom, they're not scoped.
Period :)
On Apr 4, 2014 1:41 AM, "Pentasis" [email protected] wrote:

I see. Is this a "limitation" of the polyfill or the spec?

Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-39543141
.

from grunt-vulcanize.

I understand this is not the place to ask these questions, I hope you don't mind, because this confuses me slightly. When the style is scoped it would still take up its own http-request wouldn't it? If so, does this not mean we get uber-slow loading pages once we create projects with, say a few hundred components? But perhaps I am mistaken and I misunderstand the workings of the Shadow Dom.

from grunt-vulcanize.

This is what vulcanize does. You have the option of concatenating all HTML Imports into a single import as well as inlining all resources using --inline. Using that option minimizes requests. See:

view-source:http://www.polymer-project.org/elements/common_elements.vulcanized.html?20140404

from grunt-vulcanize.