Very excited for this feature! On Thu, Sep 8, 2011 at 2:28 PM, Roland Steiner <rolandstei...@chromium.org>wrote: > > As per discussion on > http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/032056.html, > our implementation would diverge from the current HTML5 spec >
Why do diverge? It seems like we should at least prefix the attribute with webkit in the case spec changes in the future. The implementation plan is as follows: > > 1.) Add 'scoped' to HTMLStyleElement.idl and HTMLAttributeNames.in, as well > as adding the required plumbing for the attribute > 2.) Implement registering with the scoping element. For efficient matching > it is necessary that an element can quickly discern whether or not it has > <style scoped> as direct child(ren). > 3.) Implement the meat of the matching (see below) > 4.) Add support for scoped @keyframes and @font-face > > Note: https://bugs.webkit.org/show_bug.cgi?id=49142 already has a patch > for steps 1-3 that works as advertised. In order to make it easier to > review, I would just break it up into smaller chunks as outlined above. > Can we take these steps behind a flag given the attribute doesn't work properly without some steps? - Ryosuke
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev