HTML Standard Tracker

Diff (omit for latest revision)
Filter

Short URL: http://html5.org/r/7587

File a bug

SVNBugCommentTime (UTC)
7587Update font-related terminology.2012-12-17 21:53
Index: source
===================================================================
--- source	(revision 7586)
+++ source	(revision 7587)
@@ -16341,14 +16341,11 @@
   <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>
 
@@ -42189,18 +42186,15 @@
   '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>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>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>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
@@ -109581,17 +109575,14 @@
    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>
 
@@ -122098,6 +122089,7 @@
   John Boyer,
   John Bussjaeger,
   John Carpenter,
+  John Daggett,
   John Fallows,
   John Foliot,
   John Harding,

|