W3C home > Mailing lists > Public > www-style@w3.org > March 2012

<style scoped> available as experimental feature, discussing @-rules

From: Roland Steiner <rolandsteiner@google.com>
Date: Wed, 7 Mar 2012 14:46:19 +0900
Message-ID: <CACFPSpjg=QSadYGPCOQbmvAGj+mQ7PuQrehBcvhsdMQEax4aKQ@mail.gmail.com>
To: whatwg <whatwg@whatwg.org>, www-style@w3.org
Cc: Antti Koivisto <koivisto@iki.fi>, Boris Zbarsky <bzbarsky@mit.edu>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, Alex Russell <slightlyoff@google.com>, Dimitri Glazkov <dglazkov@chromium.org>, Dominic Cooney <dominicc@chromium.org>
Hi all,

First, sorry for the cross-post, I didn't know which mailing list was most
appropriate, and <style scoped> has previously been discussed on both.

Now, a shiny-new implementation of <style scoped> has made it into WebKit
and is now available as an experimental feature behind a run-time flag in
Chromium. See also the html5rocks article that has more details about it:
. As
the main developer of the WebKit implementation, I would hereby like to
solicit feedback on the feature and real-world experiences. :)

Currently, there are no known bugs, the :scope pseudo class is implemented,
but the following @-rules not yet: @font-face, @keyframes, @region, @global.

In this regard, I would also like to try to re-ignote the discussion on the
fate of @-rules within <style scoped>: As has been discussed on these
mailing lists previously, as well as informally, implementing a scoped
version of @font-face is quite difficult, and there are several voices
against even attempting it. Consequently, without an implementation of
@font-face, it may make more sense to also ignore @keyframes and @region
for consistency reasons rather than have a mix-and-match, even though the
latter 2 shouldn't be that hard to implement.

What are your thoughts on this?


- Roland
Received on Wednesday, 7 March 2012 05:47:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:13 UTC