This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15821 - The text about the scoped attribute and @font-face makes no sense
Summary: The text about the scoped attribute and @font-face makes no sense
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
Depends on:
Reported: 2012-01-31 23:58 UTC by contributor
Modified: 2012-08-27 23:17 UTC (History)
5 users (show)

See Also:


Description contributor 2012-01-31 23:58:21 UTC

The text about the scoped attribute and @font-face makes no sense

Posted from:
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0a1) Gecko/20100101 Firefox/12.0a1
Comment 1 L. David Baron (Mozilla) 2012-02-01 00:03:37 UTC
To add a bit more detail here, I'm referring to the text:

  For scoped CSS resources, the effect of other @-rules must be scoped
  to the scoped sheet and its subresources, even if the @-rule in
  question would ordinarily apply to all style sheets that affect the
  Document. Any '@page' rules in scoped CSS resources must be ignored.

    For example, an '@font-face' rule defined in a scoped style sheet
    would only define the font for the purposes of font rules in the
    scoped section; style sheets outside the scoped section using the
    same font name would not end up using that embedded font.

This seems to be based on a significant misunderstanding of what @font-face rules do.  What they do is add to the set of available fonts.  It may well make sense to scope them to a document tree, but it makes no sense to scope them to a set of rules.  For example, if the computed value of 'font-family' comes from one of the scoped rules and the computed value of 'font-style' comes from outside that set, and the scoped set defines an italic in the given family, is that considered "for the purposes of font rules in the scoped section"?  This text essentially:
 (a) requires that the computed value of all font properties that affect font selection change from their current structure to the pair of that structure with a list of all active @font-face rules, and
 (b) doesn't provide a conflict resolution algorithm for when those lists of @font-face rules differ
Comment 2 contributor 2012-07-18 16:02:28 UTC
This bug was cloned to create bug 18036 as part of operation convergence.
Comment 3 contributor 2012-08-27 23:17:05 UTC
Checked in as WHATWG revision r7289.
Check-in comment: Make @font-face in <style scoped> make more sense