[html5] r8793 - [e] (0) Better reference CSS for parsing according to CSS. Fixing https://www.w3 [...]

whatwg at whatwg.org whatwg at whatwg.org
Fri Sep 19 12:21:27 PDT 2014


Author: ianh
Date: 2014-09-19 12:21:24 -0700 (Fri, 19 Sep 2014)
New Revision: 8793

Modified:
   complete.html
   index
   source
Log:
[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

Modified: complete.html
===================================================================
--- complete.html	2014-09-19 18:35:14 UTC (rev 8792)
+++ complete.html	2014-09-19 19:21:24 UTC (rev 8793)
@@ -2435,6 +2435,10 @@
     (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 <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 @@
   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

Modified: index
===================================================================
--- index	2014-09-19 18:35:14 UTC (rev 8792)
+++ index	2014-09-19 19:21:24 UTC (rev 8793)
@@ -2435,6 +2435,10 @@
     (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 <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 @@
   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

Modified: source
===================================================================
--- source	2014-09-19 18:35:14 UTC (rev 8792)
+++ source	2014-09-19 19:21:24 UTC (rev 8793)
@@ -3132,6 +3132,12 @@
     (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 <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. <ref spec=CSSCOLOR> <ref spec=CSS></p>
@@ -61661,7 +61667,7 @@
   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



More information about the Commit-Watchers mailing list