W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2011

[whatwg] @font-face rules in <style scoped>

From: Roland Steiner <rolandsteiner@google.com>
Date: Tue, 22 Nov 2011 16:58:53 +0900
Message-ID: <CACFPSpiU-q+qq7O+SDGV-Y38KS-JdNYUFV9YPFoqiJkia7zjLg@mail.gmail.com>
On Tue, Nov 22, 2011 at 13:12, Roland Steiner <rolandsteiner at 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 at 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 Monday, 21 November 2011 23:58:53 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:38 UTC