[giow] (0) Make @font-face in <style scoped> make more sense

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=15821 Affected topics: HTML git-svn-id: http://svn.whatwg.org/webapps@7289 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Aug 27, 2012 · 1fe8eaa · 1fe8eaa
1 parent 4df6889
commit 1fe8eaa
Show file tree

Hide file tree

Showing 3 changed files with 33 additions and 18 deletions.
diff --git a/complete.html b/complete.html
@@ -16170,16 +16170,21 @@ <h4 id=the-style-element><span class=secno>4.2.6 </span>The <dfn><code>style</co
   element's descendants.</p>
 
   <p>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 <code><a href=#document>Document</a></code>. Any '@page' rules in scoped CSS resources
+  scoped to either the scoped sheet and its subresources or to the
+  subtree rooted at the <code><a href=#the-style-element>style</a></code> element's parent (if any),
+  even if the @-rule in question would ordinarily apply to all style
+  sheets that affect the <code><a href=#document>Document</a></code>, or to all nodes in the
+  <code><a href=#document>Document</a></code>. Any '@page' rules in scoped CSS resources
   must be ignored.</p>
 
   <p class=example>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.</p>
+  elements in the scoped section; the font would not be used for
+  elements outside the subtree. However, rules outside the subtree
+  that refer to font names declared in '@font-face' rules in a scoped
+  section, when those rules are inherited by nodes in the scoped
+  section, would end up referring to the fonts declared in that
+  section.</p>
 
   <hr></div>
 

diff --git a/index b/index
@@ -16170,16 +16170,21 @@ people expect to have work and what is necessary.
   element's descendants.</p>
 
   <p>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 <code><a href=#document>Document</a></code>. Any '@page' rules in scoped CSS resources
+  scoped to either the scoped sheet and its subresources or to the
+  subtree rooted at the <code><a href=#the-style-element>style</a></code> element's parent (if any),
+  even if the @-rule in question would ordinarily apply to all style
+  sheets that affect the <code><a href=#document>Document</a></code>, or to all nodes in the
+  <code><a href=#document>Document</a></code>. Any '@page' rules in scoped CSS resources
   must be ignored.</p>
 
   <p class=example>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.</p>
+  elements in the scoped section; the font would not be used for
+  elements outside the subtree. However, rules outside the subtree
+  that refer to font names declared in '@font-face' rules in a scoped
+  section, when those rules are inherited by nodes in the scoped
+  section, would end up referring to the fonts declared in that
+  section.</p>
 
   <hr></div>
 

diff --git a/source b/source
@@ -17252,16 +17252,21 @@ people expect to have work and what is necessary.
   element's descendants.</p>
 
   <p>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 <code>Document</code>. Any '@page' rules in scoped CSS resources
+  scoped to either the scoped sheet and its subresources or to the
+  subtree rooted at the <code>style</code> element's parent (if any),
+  even if the @-rule in question would ordinarily apply to all style
+  sheets that affect the <code>Document</code>, or to all nodes in the
+  <code>Document</code>. Any '@page' rules in scoped CSS resources
   must be ignored.</p>
 
   <p class="example">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.</p>
+  elements in the scoped section; the font would not be used for
+  elements outside the subtree. However, rules outside the subtree
+  that refer to font names declared in '@font-face' rules in a scoped
+  section, when those rules are inherited by nodes in the scoped
+  section, would end up referring to the fonts declared in that
+  section.</p>
 
   <hr>