On Tue, Nov 22, 2011 at 13:12, Roland Steiner <rolandsteiner@chromium.org>wrote: > I'm implementing <style scope> for WebKit at the moment, so please allow > me to add my take to some of the issues raised (although I certainly don't > claim to be an authoritative source of insight! ^_-). Comments inline: > > On Sat, Nov 19, 2011 at 10:11, Daniel Glazman < > daniel.glazman@disruptive-innovations.com> wrote: > >> Le 18/11/11 23:40, Ian Hickson a écrit : >> >> I'm happy to add clarifying text or an example to the spec if that would >>> help. >>> >> >> [cc to www-style, reply-to to www-style ] >> >> Wow, wow, wow. Slowly please. >> >> I think you should discuss that in www-style before any addition to >> html. The complete mechanism for handling scoped stylesheets will impact >> us strongly. >> >> In particular, the scoping of at-rules has NEVER ever been >> discussed with the CSS WG. If scoping @media would not be a problem >> in most cases, scoping @font-face could be an issue for rendering >> engines unable to maintain more than a document-wide list of font >> matchings at this time, ie the current state of CSS. > > > How to best implement scoped @font-face is indeed an issue I'm facing at > the moment. @keyframes is another. > To qualify that statement: I don't have a strong preference either way, but if we spec @font-face and @keyframes to be ignored in <style scoped> (for the very reasons Boris stated) just like @page is, I wouldn't shed a tear... ;) - Roland
Received on Tuesday, 22 November 2011 07:59:42 UTC