15821 2012-01-31 23:58:21 +0000 The text about the scoped attribute and @font-face makes no sense 2012-08-27 23:17:05 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#style-default-media P3 normal Unsorted 1 contributor ian bzbarsky dbaron ian jdaggett mike contributor oldest_to_newest 63480 0 contributor 2012-01-31 23:58:21 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#style-default-media Complete: http://www.whatwg.org/c#style-default-media Comment: The text about the scoped attribute and @font-face makes no sense Posted from: 84.97.147.161 User agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0a1) Gecko/20100101 Firefox/12.0a1 63484 1 dbaron 2012-02-01 00:03:37 +0000 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 70541 2 contributor 2012-07-18 16:02:28 +0000 This bug was cloned to create bug 18036 as part of operation convergence. 72871 3 contributor 2012-08-27 23:17:05 +0000 Checked in as WHATWG revision r7289. Check-in comment: Make @font-face in <style scoped> make more sense http://html5.org/tools/web-apps-tracker?from=7288&to=7289