HTML Standard Tracker


File a bug

SVNBugCommentTime (UTC)
602812526apply wg decision (introductory text for <img>)2011-04-25 23:09
@@ -144,20 +144,26 @@
    specification unambiguously disallows the use of <code>table</code>
    elements for layout purposes.</li>
    <li>The W3C version requires authors who are writing HTML e-mails
    with images to people they know can see the images (e.g. a wife
    sending her husband photos of their child) to nonetheless include
    textual alternatives to those images, because of <a
    working group decision from April 2011</a>.</li>
+   <li>The W3C version does not state that the <code>img</code>
+   element's <code title="attr-img-alt">alt</code> attribute is its
+   <span>fallback content</span>, because of <a
+   href="">a
+   working group decision from April 2011</a>.</li>
   <p>Features that are part of HTML (and this specification) but that
   are currently published as separate specifications as well, and are
   not included in the W3C HTML5 specification, consist of:</p>
   <ul class="brief">
    <li><a href="#2dcontext">Canvas 2D Graphics Context</a><!--2DCONTEXT-->
    <li><a href="#microdata">Microdata</a><!--MD-->
    <li><a href="#mdvocabs">Microdata vocabularies</a>
@@ -11617,20 +11623,23 @@ background: transparent">blue&lt;/span>.&lt;/p></pre>
   <p>Elements that are from namespaces other than the <span>HTML
   namespace</span> and that convey content but not metadata, are
   <span>embedded content</span> for the purposes of the content models
   defined in this specification. (For example, MathML, or SVG.)</p>
   <p>Some embedded content elements can have <dfn>fallback
   content</dfn>: content that is to be used when the external resource
   cannot be used (e.g. because it is of an unsupported format). The
   element definitions state what the fallback is, if any.</p>
+  <!-- we might not need to define fallback content at all. consider
+  removing it if we don't end up using it anywhere (e.g. Selection)
+  -->
   <h6>Interactive content</h6>
@@ -23363,23 +23372,29 @@ interface <dfn>HTMLImageElement</dfn> : <span>HTMLElement</span> {
        Slight hitch: their images are at a different origin, and we
        don't want to allow arbitrary cross-origin inspection (privacy
        leak risk).
      * See note at rel=noreferrer.
   <p>The image given by the <dfn
   title="attr-img-src"><code>src</code></dfn> attribute is the
-  embedded content, and the value of the <dfn
-  title="attr-img-alt"><code>alt</code></dfn> attribute is the
-  <code>img</code> element's <span>fallback content</span>.</p>
+  embedded content; the value of the <dfn
+  title="attr-img-alt"><code>alt</code></dfn> attribute provides
+  equivalent content for those who cannot process images or who have
+  image loading disabled<!--
+--><!--END w3c-html--><!--FORK--><!--
+  --> (i.e. it is the <code>img</code> element's <span>fallback
+  content</span>)<!--
+--><!--START w3c-html--><!--FORK--><!--
+  -->.</p>
   <p>The <code title="attr-img-src">src</code> attribute must be
   present, and must contain a <span>valid non-empty URL potentially
   surrounded by spaces</span> referencing a non-interactive,
   optionally animated, image resource that is neither paged nor
   <p class="note">Images can thus be static bitmaps (e.g. PNGs, GIFs,
   JPEGs), single-page vector documents (single-page PDFs, XML files
   with an SVG root element), animated bitmaps (APNGs, animated GIFs),