[html5] r3126 - [] (0) Try to make the definitions of 'available', 'supported', image.width, ima [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon May 25 16:31:39 PDT 2009
Author: ianh
Date: 2009-05-25 16:31:37 -0700 (Mon, 25 May 2009)
New Revision: 3126
Modified:
index
source
Log:
[] (0) Try to make the definitions of 'available', 'supported', image.width, image.height, and image.complete more correct.
Modified: index
===================================================================
--- index 2009-05-25 22:10:39 UTC (rev 3125)
+++ index 2009-05-25 23:31:37 UTC (rev 3126)
@@ -230,7 +230,8 @@
<li><a href=#dom-trees><span class=secno>2.1.2 </span>DOM trees</a></li>
<li><a href=#scripting-0><span class=secno>2.1.3 </span>Scripting</a></li>
<li><a href=#plugins><span class=secno>2.1.4 </span>Plugins</a></li>
- <li><a href=#character-encodings><span class=secno>2.1.5 </span>Character encodings</a></ol></li>
+ <li><a href=#character-encodings><span class=secno>2.1.5 </span>Character encodings</a></li>
+ <li><a href=#resources><span class=secno>2.1.6 </span>Resources</a></ol></li>
<li><a href=#conformance-requirements><span class=secno>2.2 </span>Conformance requirements</a>
<ol>
<li><a href=#dependencies><span class=secno>2.2.1 </span>Dependencies</a></li>
@@ -1647,8 +1648,30 @@
-->. <!-- XXX #refs RFC1345 ? --></p>
+ <h4 id=resources><span class=secno>2.1.6 </span>Resources</h4>
+ <p>The specification uses the term <i>supported</i> when referring
+ to whether a user agent has an implementation capable of decoding
+ the semantics of an external resource. A format or type is said to
+ be <i>supported</i> if the implementation can process an external
+ resource of that format or type without critical aspects of the
+ resource being ignored. Whether a specific resource is
+ <i>supported</i> can depend on what features of the resource's
+ format are in use.</p>
+ <p class=example>For example, a PNG image would be considered to
+ be in a supported format if its pixel data could be decoded and
+ rendered, even if, unbeknownst to the implementation, the image
+ actually also contained animation data.</p>
+
+ <p class=example>A MPEG4 video file would not be considered to be
+ in a supported format if the compression format used was not
+ supported, even if the implementation could determine the dimensions
+ of the movie from the file's metadata.</p>
+
+
+
+
<h3 id=conformance-requirements><span class=secno>2.2 </span>Conformance requirements</h3>
<p>All diagrams, examples, and notes in this specification are
@@ -17362,29 +17385,30 @@
<a href=#origin-0 title=origin>cross-origin</a> access control policies
that mitigate this attack.</p>
- <p>If the image's type is a supported image type, and the image is a
- valid image of that type, then the image is said to be
- <i>available</i> (this affects exactly what the element represents,
- as defined below). This can be true even before the image is
- completely downloaded, if the user agent supports incremental
- rendering of images; in such cases, each <a href=#concept-task title=concept-task>task</a> that is <a href=#queue-a-task title="queue a
+ <p>If the image is in a supported image type and its dimensions are
+ known, then the image is said to be <dfn id=img-available title=img-available><i>available</i></dfn> (this affects exactly
+ what the element represents, as defined below). This can be true
+ even before the image is completely downloaded, if the user agent
+ supports incremental rendering of images; in such cases, each <a href=#concept-task title=concept-task>task</a> that is <a href=#queue-a-task title="queue a
task">queued</a> by the <a href=#networking-task-source>networking task source</a> while
the image is being <a href=#fetch title=fetch>fetched</a> must update
- the presentation of the image appropriately.</p>
+ the presentation of the image appropriately. It can also stop being
+ true, e.g. if the user agent finds, after obtaining the image's
+ dimensions, that the image data is actually fatally corrupted.</p>
<p>If the image was not fetched (e.g. because the UA's image support
is disabled, or because the <code title=attr-img-src><a href=#attr-img-src>src</a></code>
attribute's value is an <i>ignored self-reference</i>), or if the
conditions in the previous paragraph are not met, then the image is
- <em>not</em> <i>available</i>.</p>
+ <em>not</em> <i title=img-available><a href=#img-available>available</a></i>.</p>
- <p class=note>An image might be <i>available</i> in one
- <a href=#view>view</a> but not another. For instance, a
- <code>Document</code> could be rendered by a screen reader providing
- a speech synthesis view of the output of a Web browser using the
- screen media. In this case, the image would be <i>available</i> in
- the Web browser's screen view, but <em>not</em> <i>available</i> in
- the screen reader's view.</p>
+ <p class=note>An image might be <i title=img-available><a href=#img-available>available</a></i> in one <a href=#view>view</a> but not
+ another. For instance, a <code>Document</code> could be rendered by
+ a screen reader providing a speech synthesis view of the output of a
+ Web browser using the screen media. In this case, the image would be
+ <i title=img-available><a href=#img-available>available</a></i> in the Web browser's screen
+ view, but <em>not</em> <i title=img-available><a href=#img-available>available</a></i> in the
+ screen reader's view.</p>
<p>Whether the image is fetched successfully or not (e.g. whether
the response code was a 2xx code <a href=#concept-http-equivalent-codes title=concept-http-equivalent-codes>or equivalent</a>) must be
@@ -17415,8 +17439,8 @@
<p>The <a href=#concept-task title=concept-task>task</a> that is <a href=#queue-a-task title="queue a task">queued</a> by the <a href=#networking-task-source>networking task
source</a> once the resource has been <a href=#fetch title=fetch>fetched</a>, must, if the download was successful
- and the image is <i>available</i>, <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-load><a href=#event-load>load</a></code> at the <code><a href=#the-img-element>img</a></code> element (this
+ and the image is <i title=img-available><a href=#img-available>available</a></i>, <a href=#queue-a-task>queue
+ a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-load><a href=#event-load>load</a></code> at the <code><a href=#the-img-element>img</a></code> element (this
happens after <code title=dom-img-complete><a href=#dom-img-complete>complete</a></code> starts
returning true); and otherwise, if the fetching process fails
without a response from the remote server, or completes but the
@@ -17439,8 +17463,8 @@
the content, redundant with some other information in the
document.</p>
- <p>If the image is <i>available</i> and the user agent is
- configured to display that image, then the element
+ <p>If the image is <i title=img-available><a href=#img-available>available</a></i> and the
+ user agent is configured to display that image, then the element
<a href=#represents>represents</a> the image specified by the <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute.</p>
<p>Otherwise, the element <a href=#represents>represents</a> nothing, and may
@@ -17459,8 +17483,8 @@
<p>The image is a key part of the content; the <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code> attribute gives a textual
equivalent or replacement for the image.</p>
- <p>If the image is <i>available</i> and the user agent is
- configured to display that image, then the element
+ <p>If the image is <i title=img-available><a href=#img-available>available</a></i> and the
+ user agent is configured to display that image, then the element
<a href=#represents>represents</a> the image specified by the <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute.</p>
<p>Otherwise, the element <a href=#represents>represents</a> the text given
@@ -17482,16 +17506,16 @@
is a key part of the content but that a textual replacement for
the image was not available when the image was generated.</p>
- <p>If the image is <i>available</i>, the element
- <a href=#represents>represents</a> the image specified by the <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute.</p>
+ <p>If the image is <i title=img-available><a href=#img-available>available</a></i>, the
+ element <a href=#represents>represents</a> the image specified by the <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute.</p>
- <p>If the image is not <i>available</i> or if the user agent is
- not configured to display the image, then the user agent should
- display some sort of indicator that there is an image that is not
- being rendered, and may, if requested by the user, or if so
- configured, or when required to provide contextual information in
- response to navigation, provide caption information for the image,
- derived as follows:</p>
+ <p>If the image is not <i title=img-available><a href=#img-available>available</a></i> or
+ if the user agent is not configured to display the image, then the
+ user agent should display some sort of indicator that there is an
+ image that is not being rendered, and may, if requested by the
+ user, or if so configured, or when required to provide contextual
+ information in response to navigation, provide caption information
+ for the image, derived as follows:</p>
<ol><li><p>If the image has a <code title=attr-title><a href=#the-title-attribute>title</a></code>
attribute whose value is not the empty string, then the value of
@@ -17621,17 +17645,18 @@
rendered width and height of the image, in CSS pixels, if the image
is being rendered, and is being rendered to a visual medium; or else
the intrinsic width and height of the image, in CSS pixels, if the
- image is <i>available</i> but not being rendered to a visual medium;
- or else 0, if the image is not <i>available</i> or its dimensions
- are not known. <a href=#refsCSS21>[CSS21]</a></p>
+ image is <i title=img-available><a href=#img-available>available</a></i> but not being
+ rendered to a visual medium; or else 0, if the image is not <i title=img-available><a href=#img-available>available</a></i> or its dimensions are not
+ known. <a href=#refsCSS21>[CSS21]</a></p>
<p>On setting, they must act as if they <a href=#reflect title=reflect>reflected</a> the respective content attributes
of the same name.</p>
<p>The DOM attribute <dfn id=dom-img-complete title=dom-img-complete><code>complete</code></dfn> must return
- true if the user agent has fetched the image specified in the <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute, and it is a valid image,
- even if the final <a href=#concept-task title=concept-task>task</a> queued by
- the <a href=#networking-task-source>networking task source</a> for the <a href=#fetch title=fetch>fetching</a> of the image resource has not yet been
+ true if the user agent has fetched the image specified in the <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute, and it is in a supported
+ image type (i.e. it was decoded without fatal errors), even if the
+ final <a href=#concept-task title=concept-task>task</a> queued by the
+ <a href=#networking-task-source>networking task source</a> for the <a href=#fetch title=fetch>fetching</a> of the image resource has not yet been
processed. Otherwise, the attribute must return false.</p>
<p class=note>The value of <code title=dom-img-complete><a href=#dom-img-complete>complete</a></code> can thus change while a
@@ -18010,9 +18035,9 @@
at least that would look good on the cover of a blue book.</p></pre>
<p>This example shows how the alternative text should be written
- such that if the image isn't <i>available</i>, and the text is used
- instead, the text flows seamlessly into the surrounding text, as
- if the image had never been there in the first place.</p>
+ such that if the image isn't <i title=img-available><a href=#img-available>available</a></i>, and the text is used instead,
+ the text flows seamlessly into the surrounding text, as if the
+ image had never been there in the first place.</p>
</div>
@@ -32424,12 +32449,11 @@
<p>If the image was successfully obtained, with no network errors,
and the image's type is a supported image type, and the image is a
- valid image of that type, then the image is said to be
- <i>available</i>. If this is true before the image is completely
- downloaded, each <a href=#concept-task title=concept-task>task</a> that is
- <a href=#queue-a-task title="queue a task">queued</a> by the <a href=#networking-task-source>networking
- task source</a> while the image is being <a href=#fetch title=fetch>fetched</a> must update the presentation of the
- image appropriately.</p>
+ valid image of that type, then the image is said to be <dfn id=input-img-available title=input-img-available><i>available</i></dfn>. If this is true
+ before the image is completely downloaded, each <a href=#concept-task title=concept-task>task</a> that is <a href=#queue-a-task title="queue a
+ task">queued</a> by the <a href=#networking-task-source>networking task source</a> while
+ the image is being <a href=#fetch title=fetch>fetched</a> must update
+ the presentation of the image appropriately.</p>
<p>The user agents should apply the <a href=#content-type-sniffing:-image title="Content-Type
sniffing: image">image sniffing rules</a> to determine the type
@@ -32447,13 +32471,14 @@
<p>The <a href=#concept-task title=concept-task>task</a> that is <a href=#queue-a-task title="queue a task">queued</a> by the <a href=#networking-task-source>networking task
source</a> once the resource has been <a href=#fetch title=fetch>fetched</a>, must, if the download was successful
- and the image is <i>available</i>, <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-load><a href=#event-load>load</a></code> at the <code><a href=#the-input-element>input</a></code> element;
- and otherwise, if the fetching process fails without a response from
- the remote server, or completes but the image is not a valid or
- supported image, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-error><a href=#event-error>error</a></code> on the
- <code><a href=#the-input-element>input</a></code> element.</p>
+ and the image is <i title=input-img-available><a href=#input-img-available>available</a></i>,
+ <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called
+ <code title=event-load><a href=#event-load>load</a></code> at the <code><a href=#the-input-element>input</a></code>
+ element; and otherwise, if the fetching process fails without a
+ response from the remote server, or completes but the image is not a
+ valid or supported image, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a
+ simple event</a> called <code title=event-error><a href=#event-error>error</a></code> on
+ the <code><a href=#the-input-element>input</a></code> element.</p>
<hr></div>
@@ -32468,9 +32493,9 @@
<div class=impl>
<hr><p>If the <code title=attr-input-src><a href=#attr-input-src>src</a></code> attribute is set,
- and the image is <i>available</i> and the user agent is configured
- to display that image, then: The element <a href=#represents>represents</a> a
- control for selecting a <a href=#concept-input-type-image-coordinate title=concept-input-type-image-coordinate>coordinate</a> from
+ and the image is <i title=input-img-available><a href=#input-img-available>available</a></i> and
+ the user agent is configured to display that image, then: The
+ element <a href=#represents>represents</a> a control for selecting a <a href=#concept-input-type-image-coordinate title=concept-input-type-image-coordinate>coordinate</a> from
the image specified by the <code title=attr-input-src><a href=#attr-input-src>src</a></code>
attribute; if the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>, the user agent should
allow the user to select this <a href=#concept-input-type-image-coordinate title=concept-input-type-image-coordinate>coordinate</a>. The
@@ -68779,14 +68804,14 @@
does not <a href=#represents title=represents>represent</a> an image, but the
element already has intrinsic dimensions (e.g. from the
<a href=#dimension-attributes>dimension attributes</a> or CSS rules), and either the user
- agent has reason to believe that the image will become
- <i>available</i> and be rendered in due course or the
- <code>Document</code> is in <a href=#quirks-mode>quirks mode</a>, the element is
- expected to be treated as a replaced element whose content is the
- text that the element represents, if any, optionally alongside an
- icon indicating that the image is being obtained. For
- <code><a href=#the-input-element>input</a></code> elements, the text is expected to appear
- button-like to indicate that the element is a <a href=#concept-button title=concept-button>button</a>.</p>
+ agent has reason to believe that the image will become <i title=img-available><a href=#img-available>available</a></i><!--input-img-available also-->
+ and be rendered in due course or the <code>Document</code> is in
+ <a href=#quirks-mode>quirks mode</a>, the element is expected to be treated as a
+ replaced element whose content is the text that the element
+ represents, if any, optionally alongside an icon indicating that the
+ image is being obtained. For <code><a href=#the-input-element>input</a></code> elements, the text
+ is expected to appear button-like to indicate that the element is a
+ <a href=#concept-button title=concept-button>button</a>.</p>
<p>When an <code><a href=#the-img-element>img</a></code> element <a href=#represents>represents</a> some
text and the user agent does not expect this to change, the element
Modified: source
===================================================================
--- source 2009-05-25 22:10:39 UTC (rev 3125)
+++ source 2009-05-25 23:31:37 UTC (rev 3126)
@@ -613,8 +613,30 @@
-->. <!-- XXX #refs RFC1345 ? --></p>
+ <h4>Resources</h4>
+ <p>The specification uses the term <i>supported</i> when referring
+ to whether a user agent has an implementation capable of decoding
+ the semantics of an external resource. A format or type is said to
+ be <i>supported</i> if the implementation can process an external
+ resource of that format or type without critical aspects of the
+ resource being ignored. Whether a specific resource is
+ <i>supported</i> can depend on what features of the resource's
+ format are in use.</p>
+ <p class="example">For example, a PNG image would be considered to
+ be in a supported format if its pixel data could be decoded and
+ rendered, even if, unbeknownst to the implementation, the image
+ actually also contained animation data.</p>
+
+ <p class="example">A MPEG4 video file would not be considered to be
+ in a supported format if the compression format used was not
+ supported, even if the implementation could determine the dimensions
+ of the movie from the file's metadata.</p>
+
+
+
+
<h3>Conformance requirements</h3>
<p>All diagrams, examples, and notes in this specification are
@@ -18600,30 +18622,33 @@
<span title="origin">cross-origin</span> access control policies
that mitigate this attack.</p>
- <p>If the image's type is a supported image type, and the image is a
- valid image of that type, then the image is said to be
- <i>available</i> (this affects exactly what the element represents,
- as defined below). This can be true even before the image is
- completely downloaded, if the user agent supports incremental
- rendering of images; in such cases, each <span
+ <p>If the image is in a supported image type and its dimensions are
+ known, then the image is said to be <dfn
+ title="img-available"><i>available</i></dfn> (this affects exactly
+ what the element represents, as defined below). This can be true
+ even before the image is completely downloaded, if the user agent
+ supports incremental rendering of images; in such cases, each <span
title="concept-task">task</span> that is <span title="queue a
task">queued</span> by the <span>networking task source</span> while
the image is being <span title="fetch">fetched</span> must update
- the presentation of the image appropriately.</p>
+ the presentation of the image appropriately. It can also stop being
+ true, e.g. if the user agent finds, after obtaining the image's
+ dimensions, that the image data is actually fatally corrupted.</p>
<p>If the image was not fetched (e.g. because the UA's image support
is disabled, or because the <code title="attr-img-src">src</code>
attribute's value is an <i>ignored self-reference</i>), or if the
conditions in the previous paragraph are not met, then the image is
- <em>not</em> <i>available</i>.</p>
+ <em>not</em> <i title="img-available">available</i>.</p>
- <p class="note">An image might be <i>available</i> in one
- <span>view</span> but not another. For instance, a
- <code>Document</code> could be rendered by a screen reader providing
- a speech synthesis view of the output of a Web browser using the
- screen media. In this case, the image would be <i>available</i> in
- the Web browser's screen view, but <em>not</em> <i>available</i> in
- the screen reader's view.</p>
+ <p class="note">An image might be <i
+ title="img-available">available</i> in one <span>view</span> but not
+ another. For instance, a <code>Document</code> could be rendered by
+ a screen reader providing a speech synthesis view of the output of a
+ Web browser using the screen media. In this case, the image would be
+ <i title="img-available">available</i> in the Web browser's screen
+ view, but <em>not</em> <i title="img-available">available</i> in the
+ screen reader's view.</p>
<p>Whether the image is fetched successfully or not (e.g. whether
the response code was a 2xx code <span
@@ -18658,8 +18683,8 @@
title="queue a task">queued</span> by the <span>networking task
source</span> once the resource has been <span
title="fetch">fetched</span>, must, if the download was successful
- and the image is <i>available</i>, <span>queue a task</span> to
- <span>fire a simple event</span> called <code
+ and the image is <i title="img-available">available</i>, <span>queue
+ a task</span> to <span>fire a simple event</span> called <code
title="event-load">load</code> at the <code>img</code> element (this
happens after <code title="dom-img-complete">complete</code> starts
returning true); and otherwise, if the fetching process fails
@@ -18690,8 +18715,8 @@
the content, redundant with some other information in the
document.</p>
- <p>If the image is <i>available</i> and the user agent is
- configured to display that image, then the element
+ <p>If the image is <i title="img-available">available</i> and the
+ user agent is configured to display that image, then the element
<span>represents</span> the image specified by the <code
title="attr-img-src">src</code> attribute.</p>
@@ -18712,8 +18737,8 @@
title="attr-img-alt">alt</code> attribute gives a textual
equivalent or replacement for the image.</p>
- <p>If the image is <i>available</i> and the user agent is
- configured to display that image, then the element
+ <p>If the image is <i title="img-available">available</i> and the
+ user agent is configured to display that image, then the element
<span>represents</span> the image specified by the <code
title="attr-img-src">src</code> attribute.</p>
@@ -18737,17 +18762,17 @@
is a key part of the content but that a textual replacement for
the image was not available when the image was generated.</p>
- <p>If the image is <i>available</i>, the element
- <span>represents</span> the image specified by the <code
+ <p>If the image is <i title="img-available">available</i>, the
+ element <span>represents</span> the image specified by the <code
title="attr-img-src">src</code> attribute.</p>
- <p>If the image is not <i>available</i> or if the user agent is
- not configured to display the image, then the user agent should
- display some sort of indicator that there is an image that is not
- being rendered, and may, if requested by the user, or if so
- configured, or when required to provide contextual information in
- response to navigation, provide caption information for the image,
- derived as follows:</p>
+ <p>If the image is not <i title="img-available">available</i> or
+ if the user agent is not configured to display the image, then the
+ user agent should display some sort of indicator that there is an
+ image that is not being rendered, and may, if requested by the
+ user, or if so configured, or when required to provide contextual
+ information in response to navigation, provide caption information
+ for the image, derived as follows:</p>
<ol>
@@ -18900,9 +18925,10 @@
rendered width and height of the image, in CSS pixels, if the image
is being rendered, and is being rendered to a visual medium; or else
the intrinsic width and height of the image, in CSS pixels, if the
- image is <i>available</i> but not being rendered to a visual medium;
- or else 0, if the image is not <i>available</i> or its dimensions
- are not known. <a href="#refsCSS21">[CSS21]</a></p>
+ image is <i title="img-available">available</i> but not being
+ rendered to a visual medium; or else 0, if the image is not <i
+ title="img-available">available</i> or its dimensions are not
+ known. <a href="#refsCSS21">[CSS21]</a></p>
<p>On setting, they must act as if they <span
title="reflect">reflected</span> the respective content attributes
@@ -18911,9 +18937,10 @@
<p>The DOM attribute <dfn
title="dom-img-complete"><code>complete</code></dfn> must return
true if the user agent has fetched the image specified in the <code
- title="attr-img-src">src</code> attribute, and it is a valid image,
- even if the final <span title="concept-task">task</span> queued by
- the <span>networking task source</span> for the <span
+ title="attr-img-src">src</code> attribute, and it is in a supported
+ image type (i.e. it was decoded without fatal errors), even if the
+ final <span title="concept-task">task</span> queued by the
+ <span>networking task source</span> for the <span
title="fetch">fetching</span> of the image resource has not yet been
processed. Otherwise, the attribute must return false.</p>
@@ -19310,9 +19337,10 @@
at least that would look good on the cover of a blue book.</p></pre>
<p>This example shows how the alternative text should be written
- such that if the image isn't <i>available</i>, and the text is used
- instead, the text flows seamlessly into the surrounding text, as
- if the image had never been there in the first place.</p>
+ such that if the image isn't <i
+ title="img-available">available</i>, and the text is used instead,
+ the text flows seamlessly into the surrounding text, as if the
+ image had never been there in the first place.</p>
</div>
@@ -36099,13 +36127,13 @@
<p>If the image was successfully obtained, with no network errors,
and the image's type is a supported image type, and the image is a
- valid image of that type, then the image is said to be
- <i>available</i>. If this is true before the image is completely
- downloaded, each <span title="concept-task">task</span> that is
- <span title="queue a task">queued</span> by the <span>networking
- task source</span> while the image is being <span
- title="fetch">fetched</span> must update the presentation of the
- image appropriately.</p>
+ valid image of that type, then the image is said to be <dfn
+ title="input-img-available"><i>available</i></dfn>. If this is true
+ before the image is completely downloaded, each <span
+ title="concept-task">task</span> that is <span title="queue a
+ task">queued</span> by the <span>networking task source</span> while
+ the image is being <span title="fetch">fetched</span> must update
+ the presentation of the image appropriately.</p>
<p>The user agents should apply the <span title="Content-Type
sniffing: image">image sniffing rules</span> to determine the type
@@ -36126,14 +36154,14 @@
title="queue a task">queued</span> by the <span>networking task
source</span> once the resource has been <span
title="fetch">fetched</span>, must, if the download was successful
- and the image is <i>available</i>, <span>queue a task</span> to
- <span>fire a simple event</span> called <code
- title="event-load">load</code> at the <code>input</code> element;
- and otherwise, if the fetching process fails without a response from
- the remote server, or completes but the image is not a valid or
- supported image, <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-error">error</code> on the
- <code>input</code> element.</p>
+ and the image is <i title="input-img-available">available</i>,
+ <span>queue a task</span> to <span>fire a simple event</span> called
+ <code title="event-load">load</code> at the <code>input</code>
+ element; and otherwise, if the fetching process fails without a
+ response from the remote server, or completes but the image is not a
+ valid or supported image, <span>queue a task</span> to <span>fire a
+ simple event</span> called <code title="event-error">error</code> on
+ the <code>input</code> element.</p>
<hr>
@@ -36153,9 +36181,9 @@
<hr>
<p>If the <code title="attr-input-src">src</code> attribute is set,
- and the image is <i>available</i> and the user agent is configured
- to display that image, then: The element <span>represents</span> a
- control for selecting a <span
+ and the image is <i title="input-img-available">available</i> and
+ the user agent is configured to display that image, then: The
+ element <span>represents</span> a control for selecting a <span
title="concept-input-type-image-coordinate">coordinate</span> from
the image specified by the <code title="attr-input-src">src</code>
attribute; if the element is <i
@@ -81022,15 +81050,15 @@
does not <span title="represents">represent</span> an image, but the
element already has intrinsic dimensions (e.g. from the
<span>dimension attributes</span> or CSS rules), and either the user
- agent has reason to believe that the image will become
- <i>available</i> and be rendered in due course or the
- <code>Document</code> is in <span>quirks mode</span>, the element is
- expected to be treated as a replaced element whose content is the
- text that the element represents, if any, optionally alongside an
- icon indicating that the image is being obtained. For
- <code>input</code> elements, the text is expected to appear
- button-like to indicate that the element is a <span
- title="concept-button">button</span>.</p>
+ agent has reason to believe that the image will become <i
+ title="img-available">available</i><!--input-img-available also-->
+ and be rendered in due course or the <code>Document</code> is in
+ <span>quirks mode</span>, the element is expected to be treated as a
+ replaced element whose content is the text that the element
+ represents, if any, optionally alongside an icon indicating that the
+ image is being obtained. For <code>input</code> elements, the text
+ is expected to appear button-like to indicate that the element is a
+ <span title="concept-button">button</span>.</p>
<p>When an <code>img</code> element <span>represents</span> some
text and the user agent does not expect this to change, the element
More information about the Commit-Watchers
mailing list