- From: Brian Kardell <bkardell@gmail.com>
- Date: Wed, 28 Nov 2012 12:51:57 -0500
- To: Marcos Caceres <w3c@marcosc.com>
- Cc: public-nextweb@w3.org
- Message-ID: <CADC=+jd8FG4txz7Sj0o76JeBXaB-YGAUZEzZ_j0BW7naSiBzLA@mail.gmail.com>
On Wed, Nov 28, 2012 at 6:40 AM, Marcos Caceres <w3c@marcosc.com> wrote: > > > > On Tuesday, November 27, 2012 at 5:40 PM, Brian Kardell wrote: > > > Anyone care to take on looking at the numerous things claiming to be > shims or polyfills for this ? > > > Sure, can you provide some pointers to any that are good/popular? > > -- > Marcos Caceres > > This is the one listed on modernizr's no BS list https://github.com/thingsinjars/jQuery-Scoped-CSS-plugin it is one of the two or three that I looked at way back... It has 37 github stars and 2 forks too, so I think it's safe to say it's had some use. Again, I think these should use data-scoped or x-scoped as there are no native implementations and recently even moves to delay that part of it - so I think this is a prollyfill if it can be done. I say if because we haven't defined/discussed fidelity or how we'd do things like this... So far we have briefly touched on tags, JS APIs and CSS - this is an attribute on a tag, related only to CSS :) so it's a bit different. My biggest concern previously was that if selector specificty gets very obviously hosed to the point where if it were implemented natively exactly according to the draft as written today and you removed the prefix everything would horribly break - then the fidelity is pretty low and potentially not worth doing... In the very least, we need some kind of way to note those sorts of expectations for prollyfills as they are (always) "experimental".
Received on Wednesday, 28 November 2012 17:52:28 UTC