[e] (0) Better reference CSS for parsing according to CSS.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=26208 Affected topics: Canvas, HTML git-svn-id: https://svn.whatwg.org/webapps@8793 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Sep 19, 2014 · bace55e · bace55e
1 parent 6848c6a
commit bace55e
Show file tree

Hide file tree

Showing 3 changed files with 17 additions and 3 deletions.
diff --git a/complete.html b/complete.html
@@ -2435,6 +2435,10 @@ <h4 id=dependencies>2.2.2 Dependencies</h4>
     (though it is encouraged, at least for Web browsers), some features are defined in terms of
     specific CSS requirements.</p>
 
+    <p>When this specification requires that something be <dfn id=parse-something-according-to-a-css-grammar><a href=http://dev.w3.org/csswg/css-syntax/#parse-something-according-to-a-css-grammar>parsed
+    according to a particular CSS grammar</a></dfn>, the relevant algorithm in the CSS Syntax
+    specification must be followed. <a href=#refsCSSSYNTAX>[CSSSYNTAX]</a></p>
+
     <p>In particular, some features require that a string be <dfn id=parsed-as-a-css-color-value>parsed as a CSS &lt;color>
     value</dfn>. When parsing a CSS value, user agents are required by the CSS specifications to
     apply some error handling rules. These apply to this specification also. <a href=#refsCSSCOLOR>[CSSCOLOR]</a> <a href=#refsCSS>[CSS]</a></p>
@@ -47241,7 +47245,7 @@ <h6 id=text-styles>4.12.4.2.5 Text styles</h6>
   object</a>.</p>
 
   <p>The <dfn id=dom-context-2d-font><code>font</code></dfn> IDL attribute, on setting, must
-  be parsed the same way as the 'font' property of CSS (but without supporting property-independent
+  be <a href=http://dev.w3.org/csswg/css-syntax/#parse-something-according-to-a-css-grammar id=text-styles:parse-something-according-to-a-css-grammar data-x-internal=parse-something-according-to-a-css-grammar>parsed the same way as the 'font' property of CSS</a> (but without supporting property-independent
   style sheet syntax like 'inherit'), and the resulting font must be assigned to the context, with
   the 'line-height' component forced to 'normal', with the 'font-size' component converted to CSS
   pixels, and with system fonts being computed to explicit values. If the new value is syntactically

diff --git a/index b/index
@@ -2435,6 +2435,10 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
     (though it is encouraged, at least for Web browsers), some features are defined in terms of
     specific CSS requirements.</p>
 
+    <p>When this specification requires that something be <dfn id=parse-something-according-to-a-css-grammar><a href=http://dev.w3.org/csswg/css-syntax/#parse-something-according-to-a-css-grammar>parsed
+    according to a particular CSS grammar</a></dfn>, the relevant algorithm in the CSS Syntax
+    specification must be followed. <a href=#refsCSSSYNTAX>[CSSSYNTAX]</a></p>
+
     <p>In particular, some features require that a string be <dfn id=parsed-as-a-css-color-value>parsed as a CSS &lt;color>
     value</dfn>. When parsing a CSS value, user agents are required by the CSS specifications to
     apply some error handling rules. These apply to this specification also. <a href=#refsCSSCOLOR>[CSSCOLOR]</a> <a href=#refsCSS>[CSS]</a></p>
@@ -47241,7 +47245,7 @@ context.fillRect(100,0,50,50); // only this square remains</pre>
   object</a>.</p>
 
   <p>The <dfn id=dom-context-2d-font><code>font</code></dfn> IDL attribute, on setting, must
-  be parsed the same way as the 'font' property of CSS (but without supporting property-independent
+  be <a href=http://dev.w3.org/csswg/css-syntax/#parse-something-according-to-a-css-grammar id=text-styles:parse-something-according-to-a-css-grammar data-x-internal=parse-something-according-to-a-css-grammar>parsed the same way as the 'font' property of CSS</a> (but without supporting property-independent
   style sheet syntax like 'inherit'), and the resulting font must be assigned to the context, with
   the 'line-height' component forced to 'normal', with the 'font-size' component converted to CSS
   pixels, and with system fonts being computed to explicit values. If the new value is syntactically

diff --git a/source b/source
@@ -3132,6 +3132,12 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
     (though it is encouraged, at least for Web browsers), some features are defined in terms of
     specific CSS requirements.</p>
 
+    <p>When this specification requires that something be <dfn data-x="parse something according to
+    a CSS grammar"
+    data-x-href="http://dev.w3.org/csswg/css-syntax/#parse-something-according-to-a-css-grammar">parsed
+    according to a particular CSS grammar</dfn>, the relevant algorithm in the CSS Syntax
+    specification must be followed. <ref spec=CSSSYNTAX></p>
+
     <p>In particular, some features require that a string be <dfn>parsed as a CSS &lt;color&gt;
     value</dfn>. When parsing a CSS value, user agents are required by the CSS specifications to
     apply some error handling rules. These apply to this specification also. <ref spec=CSSCOLOR> <ref spec=CSS></p>
@@ -61661,7 +61667,7 @@ transform. ack Shaun Morris. -->
   object</span>.</p>
 
   <p>The <dfn><code data-x="dom-context-2d-font">font</code></dfn> IDL attribute, on setting, must
-  be parsed the same way as the 'font' property of CSS (but without supporting property-independent
+  be <span data-x="parse something according to a CSS grammar">parsed the same way as the 'font' property of CSS</span> (but without supporting property-independent
   style sheet syntax like 'inherit'), and the resulting font must be assigned to the context, with
   the 'line-height' component forced to 'normal', with the 'font-size' component converted to CSS
   pixels, and with system fonts being computed to explicit values. If the new value is syntactically