Re: Decoupling <style scoped> from Shadow DOM

On Feb 20, 2014, at 6:29 PM, Hajime Morrita <morrita@google.com> wrote:
> Firefox has already shipped <style scoped> without Shadow DOM and I guess there is no dependency from scoped style to shadow DOM as the former is done before the later is started.

Looks like Firefox supports it since 21.

> WebKit situation was similar. <style scoped> was done before Shadow DOM, and style scoping for Shadow DOM was done on top of <style scoped> internals. There was no dependency from <style scoped> to Shadow DOM. And it seems both <style scoped> and non-builtin part of Shadow DOM was removed since then.
> 
> In Blink, Shadow DOM styling and <style scoped> kind of share the underlying plumbing. But it is more like that both depend on same lower-level mechanism for style scoping of DOM subtree. There is no direct dependency between both.

I had an impression that scoped style element was removed in Blink per discussion here:
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/JB8nFQXhAuQ/q_yIqFFEUVkJ

But I guess nobody proceeded to do so?
https://chromium.googlesource.com/chromium/blink/+/master/Source/core/html/HTMLStyleElement.cpp

- R. Niwa

> On Thu, Feb 20, 2014 at 6:05 PM, Erik Bryn <erik@erikbryn.com> wrote:
> Hi everyone,
> 
> First time caller, long time listener.
> 
> From what I understand, the browser vendors seem to be bundling <style scoped> with the Shadow DOM spec. I'd like to start a discussion around decoupling the two and asking that vendors prioritize shipping <style scoped> over Shadow DOM as a whole. As a web developer and JS framework author, the single most important feature that I could use immediately and I believe is totally uncontroversial is <style scoped>.
> 
> Thoughts?
> 
> Thanks,
> - Erik
> 
> 
> 
> -- 
> morrita