W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2016

Re: [csswg-drafts] [css-scoping] Support for CSS namespaces

From: Martin Janecke via GitHub <sysbot+gh@w3.org>
Date: Thu, 21 Jul 2016 09:25:03 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-234202329-1469093102-sysbot+gh@w3.org>
`<style scoped>` was ditched by Google because it was [to complex for 
Google to implement besides shadow 
DOM](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/R1x18ZLS5qQ).
 It's a pity, but it's also reality right now. Do you guys think that 
similar, equally or more complex features will have better chances to 
be implemented right now? If complexity is the problem, aiming for a 
[simpler 
feature](https://github.com/w3c/csswg-drafts/issues/270#issuecomment-231999279)
 without that complexity, but which still covers part of the use cases
 seems more sensible to me.

@ionas 
> >   Why not Tab's `&` idea, which also matched preprocessor syntax 
more closely?
>
>    Where can I read about this idea?

I think Lea refers to this: 
https://tabatkins.github.io/specs/css-nesting/

I see some benefits of the `&` idea, but having to edit `&` into every
 nested rule is a significant disadvantage too. These are different 
concepts with only some overlapping and different use cases, really.

-- 
GitHub Notification of comment by prlbr
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/270#issuecomment-234202329 
using your GitHub account
Received on Thursday, 21 July 2016 09:25:10 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:33 UTC