HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
7587Update font-related terminology.2012-12-17 21:53
@@ -16334,28 +16334,25 @@ 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 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
-  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>
+  <p class="example">For example, an '@font-face' rule defined in a scoped style sheet would only
+  define the font for the purposes of 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 family 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>
 
   <p id="title-on-style">The <dfn
   title="attr-style-title"><code>title</code></dfn> attribute on
   <code>style</code> elements defines <span>alternative style sheet
   sets</span>. If the <code>style</code> element has no <code
   title="attr-style-title">title</code> attribute, then it has no
@@ -42182,31 +42179,28 @@ hairline width with transform. ack Shaun Morris.  -->
   property of CSS (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 incorrect (including using
   property-independent style sheet syntax like 'inherit' or
   'initial'), then it must be ignored, without assigning a new font
   value. <a href="#refsCSS">[CSS]</a></p>
 
-  <p>Font names must be interpreted in the context of the <span>font style source object</span> when
-  the font is to be used; any fonts embedded using <code title="">@font-face</code> or loaded using
-  the <code>FontLoader</code> that are visible to the <span>font style source object</span> must
-  therefore be available once they are loaded. If a font is used before it is fully loaded, or if
-  the <span>font style source object</span> does not have that font in scope at the time the font is
-  to be used, then it must be treated as if it was an unknown font, falling back to another as
-  described by the relevant CSS specifications. <a href="#refsCSSFONTS">[CSSFONTS]</a></p>
-
-  <p>Only vector fonts should be used by the user agent; if a user
-  agent were to use bitmap fonts then transformations would likely
-  make the font look very ugly.</p>
+  <p>Font family names must be interpreted in the context of the <span>font style source
+  object</span> when the font is to be used; any fonts embedded using <code
+  title="">@font-face</code> or loaded using the <code>FontLoader</code> that are visible to the
+  <span>font style source object</span> must therefore be available once they are loaded. If a font
+  is used before it is fully loaded, or if the <span>font style source object</span> does not have
+  that font in scope at the time the font is to be used, then it must be treated as if it was an
+  unknown font, falling back to another as described by the relevant CSS specifications. <a
+  href="#refsCSSFONTS">[CSSFONTS]</a></p>
 
   <p>On getting, the <code title="dom-context-2d-font">font</code>
   attribute must return the <span title="serializing a CSS
   value">serialized form</span> of the current font of the context
   (with no 'line-height' component). <a
   href="#refsCSSOM">[CSSOM]</a></p>
 
   <div class="example">
 
    <p>For example, after the following statement:</p>
@@ -109574,31 +109568,28 @@ document.body.appendChild(text);
    literal string "<code title="">--&gt;</code>", then when the result
    of serializing the element is parsed, the comment will be truncated
    at that point and the rest of the comment will be interpreted as
    markup. More examples would be making a <code>script</code> element
    contain a <code>Text</code> node with the text string
    "<code>&lt;/script></code>", or having a <code>p</code> element
    that contains a <code>ul</code> element (as the <code>ul</code>
    element's <span title="syntax-start-tag">start tag</span> would
    imply the end tag for the <code>p</code>).</p>
 
-   <p>This can enable cross-site scripting attacks. An example of this
-   would be a page that lets the user enter some font names that are
-   then inserted into a CSS <code>style</code> block via the DOM and
-   which then uses the <code title="dom-innerHTML">innerHTML</code>
-   IDL attribute to get the HTML serialization of that
-   <code>style</code> element: if the user enters
-   "<code>&lt;/style>&lt;script>attack&lt;/script></code>" as a font
-   name, <code title="dom-innerHTML">innerHTML</code> will return
-   markup that, if parsed in a different context, would contain a
-   <code>script</code> node, even though no <code>script</code> node
-   existed in the original DOM.</p>
+   <p>This can enable cross-site scripting attacks. An example of this would be a page that lets the
+   user enter some font family names that are then inserted into a CSS <code>style</code> block via
+   the DOM and which then uses the <code title="dom-innerHTML">innerHTML</code> IDL attribute to get
+   the HTML serialization of that <code>style</code> element: if the user enters
+   "<code>&lt;/style>&lt;script>attack&lt;/script></code>" as a font family name, <code
+   title="dom-innerHTML">innerHTML</code> will return markup that, if parsed in a different context,
+   would contain a <code>script</code> node, even though no <code>script</code> node existed in the
+   original DOM.</p>
 
   </div>
 
   <p><dfn id="escapingString">Escaping a string</dfn> (for the
   purposes of the algorithm above) consists of running the following
   steps:</p>
 
   <ol>
 
    <li><p>Replace any occurrence of the "<code title="">&amp;</code>"
@@ -122091,20 +122082,21 @@ if (s = prompt('What is your name?')) {
   Jirka Kosek,
   Jjgod Jiang,
   Jo&atilde;o Eiras,
   Joe Clark,
   Joe Gregorio,
   Joel Spolsky,
   Johan Herland,
   John Boyer,
   John Bussjaeger,
   John Carpenter,
+  John Daggett,
   John Fallows,
   John Foliot,
   John Harding,
   John Keiser,
   John Snyders,
   John Stockton,
   John-Mark Bell,
   Johnny Stenback,
   Jon Ferraiolo,
   Jon Gibbins,

|