HTML Standard Tracker


File a bug

SVNBugCommentTime (UTC)
2131[Tools] Minor fixes: Ignore out-of-band encoding if it's not supported; require 2d context's 'font' attribute to ignore errors on setting.2008-09-02 03:35
@@ -20071,22 +20071,24 @@ notes on what would need to be defined for dashed lines:
   must return false.</p>
   <h6>Text</h6> <!-- a v3 feature -->
   <p>The <dfn title="dom-context-2d-font"><code>font</code></dfn> DOM
   attribute, on setting, must be parsed the same way as the 'font'
   property of CSS (but without supporting property-independent
   stylesheet syntax like 'inherit'), and the resulting font must be
   assigned to the context, with the 'line-height' component forced to
-  'normal'. <a href="#refsCSS">[CSS]</a><!-- XXX generic
-  version-independent reference --></p>
+  'normal'. If the new value is syntactically incorrect, then it must
+  be ignored, without assigning a new font value. <a
+  href="#refsCSS">[CSS]</a><!-- XXX generic version-independent
+  reference --></p>
   <p>Font names must be interpreted in the context of the
   <code>canvas</code> element's stylesheets; any fonts embedded using
   <code title="">@font-face</code> must therefore be available. <a
   <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>
@@ -43658,22 +43660,22 @@ interface <dfn>MessageChannel</dfn> {
   and all the bytes available so far, and returns an encoding and a
   <dfn title="concept-encoding-confidence">confidence</dfn>. The
   confidence is either <i>tentative</i> or <i>certain</i>. The
   encoding used, and whether the confidence in that encoding is
   <i>tentative</i> or <i>confident</i>, is <a
   href="#meta-charset-during-parse">used during the parsing</a> to
   determine whether to <span>change the encoding</span>.</p>
-   <li><p>If the transport layer specifies an encoding, return that
-   encoding with the <span
+   <li><p>If the transport layer specifies an encoding, and it is
+   supported, return that encoding with the <span
    <i>certain</i>, and abort these steps.</p></li>
    <li><p>The user agent may wait for more bytes of the resource to be
    available, either in this step or at any later step in this
    algorithm. For instance, a user agent might wait 500ms or 512
    bytes, whichever came first. In general preparsing the source to
    find the encoding improves performance, as it reduces the need to
    throw away the data structures used when parsing upon finding the
    encoding information. However, if the user agent delays too long to
@@ -50048,21 +50050,21 @@
    <li>Whether the document is set to <i>no quirks mode</i>,
    <i>limited quirks mode</i>, or <i>quirks mode</i></li>
    <li>The association between form controls and forms that aren't
    their nearest <code>form</code> element ancestor (use of the
    <span><code>form</code> element pointer</span> in the parser)</li>
-  <p class="note">The mutatiosn allowed by this section apply
+  <p class="note">The mutations allowed by this section apply
   <em>after</em> the <span>HTML parser</span>'s rules have been
   applied. For example, a <code title="">&lt;a::></code> start tag
   will be closed by a <code title="">&lt;/a::></code> end tag, and
   never by a <code title="">&lt;/aU0003AU0003A></code> end tag, even
   if the user agent is using the rules above to then generate an
   actual element in the DOM with the name <code
   title="">aU0003AU0003A</code> for that start tag.</p>