- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 18 Feb 2011 08:47:19 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv24119
Modified Files:
association-of-controls-and-forms.html
common-microsyntaxes.html dnd.html grouping-content.html
history.html links.html number-state.html references.html
rendering.html scripting-1.html spec.html
states-of-the-type-attribute.html text-level-semantics.html
the-button-element.html video.html webappapis.html
Log Message:
mention /favicon.ico (whatwg r5904)
[updated by splitter]
Index: text-level-semantics.html
===================================================================
RCS file: /sources/public/html5/spec/text-level-semantics.html,v
retrieving revision 1.1025
retrieving revision 1.1026
diff -u -d -r1.1025 -r1.1026
--- text-level-semantics.html 14 Feb 2011 23:51:13 -0000 1.1025
+++ text-level-semantics.html 18 Feb 2011 08:47:04 -0000 1.1026
@@ -2037,8 +2037,12 @@
<p>Any content inside <code><a href="#the-br-element">br</a></code> elements must not be
considered part of the surrounding text.</p>
- <p class="note">A <code><a href="#the-br-element">br</a></code> element separates paragraphs for
- the purposes of the Unicode bidirectional algorithm. <a href="references.html#refsBIDI">[BIDI]</a></p>
+ <p>A <code><a href="#the-br-element">br</a></code> element should separate paragraphs for the
+ purposes of the Unicode bidirectional algorithm. This requirement
+ may be implemented indirectly through the style layer. For example,
+ an HTML+CSS user agent could implement these requirements by
+ implementing the CSS 'unicode-bidi' property. <a href="references.html#refsBIDI">[BIDI]</a> <a href="references.html#refsCSS">[CSS]</a></p>
+
</div><h4 id="the-wbr-element"><span class="secno">4.6.26 </span>The <dfn><code>wbr</code></dfn> element</h4><dl class="element"><dt>Categories</dt>
<dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
Index: scripting-1.html
===================================================================
RCS file: /sources/public/html5/spec/scripting-1.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -d -r1.40 -r1.41
--- scripting-1.html 14 Feb 2011 23:51:12 -0000 1.40
+++ scripting-1.html 18 Feb 2011 08:46:58 -0000 1.41
@@ -409,11 +409,14 @@
<code title="attr-script-src"><a href="#attr-script-src">src</a></code> attribute. If the language
is not that described by "<code title="">text/javascript</code>",
then the <code title="attr-script-type"><a href="#attr-script-type">type</a></code> attribute must
- be present, as described below.</p><p>When used to include data blocks (as opposed to scripts), the
+ be present, as described below. Whatever language is used, the
+ contents of the <code><a href="#script">script</a></code> element must conform with the
+ requirements of that language's specification.</p><p>When used to include data blocks (as opposed to scripts), the
data must be embedded inline, the format of the data must be given
- using the <code title="attr-script-type"><a href="#attr-script-type">type</a></code> attribute, and
- the <code title="attr-script-src"><a href="#attr-script-src">src</a></code> attribute must not be
- specified.</p><p>The <dfn id="attr-script-type" title="attr-script-type"><code>type</code></dfn>
+ using the <code title="attr-script-type"><a href="#attr-script-type">type</a></code> attribute, the
+ <code title="attr-script-src"><a href="#attr-script-src">src</a></code> attribute must not be
+ specified, and the contents of the <code><a href="#script">script</a></code> element must
+ conform to the requirements defined for the format used.</p><p>The <dfn id="attr-script-type" title="attr-script-type"><code>type</code></dfn>
attribute gives the language of the script or format of the data. If
the attribute is present, its value must be a <a href="infrastructure.html#valid-mime-type">valid MIME
type</a>. The <code title="">charset</code> parameter must not be
Index: association-of-controls-and-forms.html
===================================================================
RCS file: /sources/public/html5/spec/association-of-controls-and-forms.html,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -d -r1.63 -r1.64
--- association-of-controls-and-forms.html 14 Feb 2011 23:51:08 -0000 1.63
+++ association-of-controls-and-forms.html 18 Feb 2011 08:46:46 -0000 1.64
@@ -860,6 +860,11 @@
selection, this must set the cursor to be just before the character
with offset <var title="">end</var>.</p>
+ <p>All elements to which this API applies have either a selection or
+ a text entry cursor position at all times (even for elements that
+ are not <a href="rendering.html#being-rendered">being rendered</a>). User agents should follow
+ platform conventions to determine their initial state.</p>
+
</div><div class="example">
<p>To obtain the currently selected text, the following JavaScript
Index: history.html
===================================================================
RCS file: /sources/public/html5/spec/history.html,v
retrieving revision 1.1033
retrieving revision 1.1034
diff -u -d -r1.1033 -r1.1034
--- history.html 3 Feb 2011 20:57:39 -0000 1.1033
+++ history.html 18 Feb 2011 08:46:57 -0000 1.1034
@@ -2063,10 +2063,21 @@
persisted user state</a>, but its URL has a fragment identifier,
<a href="#scroll-to-the-fragment-identifier">scroll to the fragment identifier</a>.</p></li>
- <li><p>If the entry is <a href="#an-entry-with-persisted-user-state">an entry with persisted user
- state</a>, the user agent may update aspects of the document and
- its rendering, for instance the scroll position or values of form
- fields, that it had previously recorded.</p></li>
+ <li>
+
+ <p>If the entry is <a href="#an-entry-with-persisted-user-state">an entry with persisted user
+ state</a>, the user agent may update aspects of the document
+ and its rendering, for instance the scroll position or values of
+ form fields, that it had previously recorded.</p>
+
+ <!-- see similar paragraphs in the textarea and input sections -->
+ <p class="note">This can even include updating the <code title="attr-dir"><a href="elements.html#the-dir-attribute">dir</a></code> attribute of <code><a href="the-button-element.html#the-textarea-element">textarea</a></code>
+ elements or <code><a href="the-input-element.html#the-input-element">input</a></code> elements whose <code title="attr-input-type"><a href="the-input-element.html#attr-input-type">type</a></code> attribute is in either the
+ <a href="states-of-the-type-attribute.html#text-state-and-search-state" title="attr-input-type-text">Text</a> state or the <a href="states-of-the-type-attribute.html#text-state-and-search-state" title="attr-input-type-search">Search</a> state, if the
+ persisted state includes the directionality of user input in such
+ controls.</p>
+
+ </li>
<li><p>If the entry is a <a href="#state-object">state object</a> entry, let <var title="">state</var> be a <a href="common-dom-interfaces.html#structured-clone">structured clone</a> of that
state object. Otherwise, let <var title="">state</var> be
Index: rendering.html
===================================================================
RCS file: /sources/public/html5/spec/rendering.html,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -d -r1.68 -r1.69
--- rendering.html 14 Feb 2011 23:51:12 -0000 1.68
+++ rendering.html 18 Feb 2011 08:46:58 -0000 1.69
@@ -552,12 +552,12 @@
margin-top: 0; margin-bottom: 0;
}
-h1 { margin-top: 0.67em; margin-bottom; 0.67em; }
-h2 { margin-top: 0.83em; margin-bottom; 0.83em; }
-h3 { margin-top: 1.00em; margin-bottom; 1.00em; }
-h4 { margin-top: 1.33em; margin-bottom; 1.33em; }
-h5 { margin-top: 1.67em; margin-bottom; 1.67em; }
-h6 { margin-top: 2.33em; margin-bottom; 2.33em; }
+h1 { margin-top: 0.67em; margin-bottom: 0.67em; }
+h2 { margin-top: 0.83em; margin-bottom: 0.83em; }
+h3 { margin-top: 1.00em; margin-bottom: 1.00em; }
+h4 { margin-top: 1.33em; margin-bottom: 1.33em; }
+h5 { margin-top: 1.67em; margin-bottom: 1.67em; }
+h6 { margin-top: 2.33em; margin-bottom: 2.33em; }
dd { margin-left: 40px; } /* <a href="#ltr-specific">LTR-specific</a>: use 'margin-right' for rtl elements */
dir, menu, ol, ul { padding-left: 40px; } /* <a href="#ltr-specific">LTR-specific</a>: use 'padding-right' for rtl elements */
@@ -2358,8 +2358,6 @@
vertical-align: top;
}
-applet[align=bottom], embed[align=bottom], iframe[align=bottom],
-img[align=bottom], input[type=image][align=bottom], object[align=bottom],
applet[align=baseline], embed[align=baseline], iframe[align=baseline],
img[align=baseline], input[type=image][align=baseline], object[align=baseline] { /* <a href="#case-insensitive-selector-exception">case-insensitive</a> */
vertical-align: baseline;
Index: grouping-content.html
===================================================================
RCS file: /sources/public/html5/spec/grouping-content.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -d -r1.31 -r1.32
--- grouping-content.html 14 Feb 2011 23:51:11 -0000 1.31
+++ grouping-content.html 18 Feb 2011 08:46:57 -0000 1.32
@@ -548,14 +548,15 @@
block of computer output the <code><a href="#the-pre-element">pre</a></code> element can be used
with a <code><a href="text-level-semantics.html#the-samp-element">samp</a></code> element. Similarly, the <code><a href="text-level-semantics.html#the-kbd-element">kbd</a></code>
element can be used within a <code><a href="#the-pre-element">pre</a></code> element to indicate
- text that the user is to enter.</p><p class="note">A newline in a <code><a href="#the-pre-element">pre</a></code> element separates
+ text that the user is to enter.</p><div class="impl">
+
+ <p>A newline in a <code><a href="#the-pre-element">pre</a></code> element should separate
paragraphs for the purposes of the Unicode bidirectional algorithm.
- <a href="references.html#refsBIDI">[BIDI]</a></p><p>If the element's <code title="attr-dir"><a href="elements.html#the-dir-attribute">dir</a></code> attribute is
- in the <i title="attr-dir-auto-state"><a href="elements.html#attr-dir-auto-state">auto</a></i> state, then for the
- purposes of the bidirectional algorithm, the user agent must <span class="XXX">act in a manner consistent with the CSS 'white-space:plaintext' feature<!-- see bug 11734 --></span>.
This requirement may be implemented indirectly through the style
layer. For example, an HTML+CSS user agent could implement these
- requirements by implementing the CSS 'unicode-bidi' property. <a href="references.html#refsCSS">[CSS]</a></p><div class="example">
+ requirements by implementing the CSS 'unicode-bidi' property. <a href="references.html#refsBIDI">[BIDI]</a> <a href="references.html#refsCSS">[CSS]</a></p>
+
+ </div><div class="example">
<p>In the following snippet, a sample of computer code is
presented.</p>
Index: video.html
===================================================================
RCS file: /sources/public/html5/spec/video.html,v
retrieving revision 1.915
retrieving revision 1.916
diff -u -d -r1.915 -r1.916
--- video.html 14 Feb 2011 23:51:15 -0000 1.915
+++ video.html 18 Feb 2011 08:47:17 -0000 1.916
@@ -2973,7 +2973,9 @@
flag</a> to false.</p></li>
</ol><hr><p>When the <dfn id="dom-media-pause" title="dom-media-pause"><code>pause()</code></dfn>
- method is invoked, the user agent must run the following steps:</p>
+ method is invoked, and when the user agent is required to pause the
+ <a href="#media-element">media element</a>, the user agent must run the following
+ steps:</p>
<ol><li><p>If the <a href="#media-element">media element</a>'s <code title="dom-media-networkState"><a href="#dom-media-networkstate">networkState</a></code> attribute has
the value <code title="dom-media-NETWORK_EMPTY"><a href="#dom-media-network_empty">NETWORK_EMPTY</a></code>, invoke the
@@ -3099,15 +3101,15 @@
<li><p>If the time was reached through the usual monotonic increase
of the current playback position during normal playback, and there
- are <a href="#text-track-cue" title="text track cue">cues</a> in <var title="">other cues</var> that have both their <a href="#text-track-cue-active-flag">text track
- cue active flag</a> set and their <a href="#text-track-cue-pause-on-exit-flag">text track cue
- pause-on-exit flag</a> set, then immediately act as if the
- element's <code title="dom-media-pause"><a href="#dom-media-pause">pause()</a></code> method had
- been invoked. <!-- pause() can in theory call load(), but never can
- it do so as part of this invokation, since we wouldn't be in this
- algorithm if the media element was empty. So, no need to couch all
- this in a task. --> (In the other cases, such as explicit seeks,
- playback is not paused by going past the end time of a <a href="#text-track-cue" title="text track cue">cue</a>, even if that <a href="#text-track-cue" title="text
+ are <a href="#text-track-cue" title="text track cue">cues</a> in <var title="">other
+ cues</var> that have both their <a href="#text-track-cue-active-flag">text track cue active
+ flag</a> set and their <a href="#text-track-cue-pause-on-exit-flag">text track cue pause-on-exit
+ flag</a> set, then immediately <a href="#dom-media-pause" title="dom-media-pause">pause</a> the <a href="#media-element">media
+ element</a>. <!-- "pause" can in theory call load(), but never
+ can it do so as part of this invokation, since we wouldn't be in
+ this algorithm if the media element was empty. So, no need to couch
+ all this in a task. --> (In the other cases, such as explicit
+ seeks, playback is not paused by going past the end time of a <a href="#text-track-cue" title="text track cue">cue</a>, even if that <a href="#text-track-cue" title="text
track cue">cue</a> has its <a href="#text-track-cue-pause-on-exit-flag">text track cue pause-on-exit
flag</a> set.)</p></li>
@@ -3161,19 +3163,34 @@
track</a>.</p>
<!--KEEP-START w3c-html--><!--TT-->
- <p>When a <a href="#media-element">media element</a> is <a href="infrastructure.html#remove-an-element-from-a-document" title="remove an
- element from a document">removed from a
- <code>Document</code></a>, if the <a href="#media-element">media element</a>'s
- <code title="dom-media-networkState"><a href="#dom-media-networkstate">networkState</a></code> attribute
- has a value other than <code title="dom-media-NETWORK_EMPTY"><a href="#dom-media-network_empty">NETWORK_EMPTY</a></code> then the user
- agent must act as if the <code title="dom-media-pause"><a href="#dom-media-pause">pause()</a></code> method had been invoked.</p>
-
<p class="note">If the <a href="#media-element">media element</a>'s
<code><a href="infrastructure.html#document">Document</a></code> stops being a <a href="browsers.html#fully-active">fully active</a>
document, then the playback will <a href="#media-playback">stop</a>
until the document is active again.</p>
- </div><h5 id="seeking"><span class="secno">4.8.10.9 </span>Seeking</h5><dl class="domintro"><dt><var title="">media</var> . <code title="dom-media-seeking"><a href="#dom-media-seeking">seeking</a></code></dt>
+ <p>When a <a href="#media-element">media element</a> is <a href="infrastructure.html#remove-an-element-from-a-document" title="remove an
+ element from a document">removed from a
+ <code>Document</code></a>, the user agent must run
+ the following steps:</p>
+
+ <ol><li><p>Asynchronously <a href="webappapis.html#await-a-stable-state">await a stable state</a>, allowing
+ the <a href="webappapis.html#concept-task" title="concept-task">task</a> that removed the
+ <a href="#media-element">media element</a> from the <code><a href="infrastructure.html#document">Document</a></code> to
+ continue. The <a href="webappapis.html#synchronous-section">synchronous section</a> consists of all the
+ remaining steps of this algorithm. (Steps in the <a href="webappapis.html#synchronous-section">synchronous
+ section</a> are marked with ⌛.)</p></li>
+
+ <li><p>⌛ If the <a href="#media-element">media element</a> is <a href="infrastructure.html#in-a-document">in a
+ <code>Document</code></a>, abort these steps.</p></li>
+
+ <li><p>⌛ If the <a href="#media-element">media element</a>'s <code title="dom-media-networkState"><a href="#dom-media-networkstate">networkState</a></code> attribute has
+ the value <code title="dom-media-NETWORK_EMPTY"><a href="#dom-media-network_empty">NETWORK_EMPTY</a></code>, abort these
+ steps.</p></li>
+
+ <li><p>⌛ <a href="#dom-media-pause" title="dom-media-pause">Pause</a> the
+ <a href="#media-element">media element</a>.</p>
+
+ </li></ol></div><h5 id="seeking"><span class="secno">4.8.10.9 </span>Seeking</h5><dl class="domintro"><dt><var title="">media</var> . <code title="dom-media-seeking"><a href="#dom-media-seeking">seeking</a></code></dt>
<dd>
Index: states-of-the-type-attribute.html
===================================================================
RCS file: /sources/public/html5/spec/states-of-the-type-attribute.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -d -r1.32 -r1.33
--- states-of-the-type-attribute.html 3 Feb 2011 20:57:42 -0000 1.32
+++ states-of-the-type-attribute.html 18 Feb 2011 08:47:04 -0000 1.33
@@ -445,6 +445,7 @@
element's <a href="association-of-controls-and-forms.html#concept-fe-value" title="concept-fe-value">value</a>.</p>
<!-- this next bit is also in the <textarea> section -->
+ <!-- and something similar is in the session history section -->
<p>If the element is <i title="concept-input-mutable"><a href="the-input-element.html#concept-input-mutable">mutable</a></i>,
the user agent should allow the user to change the writing direction
of the element, setting it either to a left-to-right writing
Index: references.html
===================================================================
RCS file: /sources/public/html5/spec/references.html,v
retrieving revision 1.1032
retrieving revision 1.1033
diff -u -d -r1.1032 -r1.1033
--- references.html 14 Feb 2011 23:51:12 -0000 1.1032
+++ references.html 18 Feb 2011 08:46:57 -0000 1.1033
@@ -616,8 +616,7 @@
Section 4.6.2. OpenSearch.org.</dd>
<dt id="refsORIGIN">[ORIGIN]</dt>
- <dd><cite><a href="http://tools.ietf.org/html/draft-ietf-websec-origin">The HTTP
- Origin Header</a></cite>, A. Barth. IETF.</dd>
+ <dd><cite><a href="http://tools.ietf.org/html/draft-ietf-websec-origin">The Web Origin Concept</a></cite>, A. Barth. IETF.</dd>
<dt id="refsPINGBACK">[PINGBACK]</dt>
<dd><cite><a href="http://www.hixie.ch/specs/pingback/pingback">Pingback
Index: the-button-element.html
===================================================================
RCS file: /sources/public/html5/spec/the-button-element.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -d -r1.49 -r1.50
--- the-button-element.html 14 Feb 2011 23:51:13 -0000 1.49
+++ the-button-element.html 18 Feb 2011 08:47:04 -0000 1.50
@@ -1292,10 +1292,13 @@
a <code><a href="#the-textarea-element">textarea</a></code> control must be initially the empty
string.</p>
- </div><p class="note">A newline in a <code><a href="#the-textarea-element">textarea</a></code> element, and in
- its <a href="#concept-textarea-raw-value" title="concept-textarea-raw-value">raw value</a>,
- separates paragraphs for the purposes of the Unicode bidirectional
- algorithm. <a href="references.html#refsBIDI">[BIDI]</a></p><p>The <dfn id="attr-textarea-readonly" title="attr-textarea-readonly"><code>readonly</code></dfn> attribute
+ <p>A newline in a <code><a href="#the-textarea-element">textarea</a></code> element, and in its <a href="#concept-textarea-raw-value" title="concept-textarea-raw-value">raw value</a>, should separate
+ paragraphs for the purposes of the Unicode bidirectional algorithm.
+ This requirement may be implemented indirectly through the style
+ layer. For example, an HTML+CSS user agent could implement these
+ requirements by implementing the CSS 'unicode-bidi' property. <a href="references.html#refsBIDI">[BIDI]</a> <a href="references.html#refsCSS">[CSS]</a></p>
+
+ </div><p>The <dfn id="attr-textarea-readonly" title="attr-textarea-readonly"><code>readonly</code></dfn> attribute
is a <a href="common-microsyntaxes.html#boolean-attribute">boolean attribute</a> used to control whether the text
can be edited by the user or not.</p><div class="impl">
@@ -1336,6 +1339,7 @@
attribute.</p>
<!-- this next bit is also in the <input> Text/Search section -->
+ <!-- and something similar is in the session history section -->
<p>If the element is <a href="#concept-textarea-mutable" title="concept-textarea-mutable">mutable</a>, the user agent
should allow the user to change the writing direction of the
element, setting it either to a left-to-right writing direction or a
@@ -1458,12 +1462,7 @@
attribute represents the element's name. The <code title="attr-fe-disabled"><a href="association-of-controls-and-forms.html#attr-fe-disabled">disabled</a></code> attribute is used to make
the control non-interactive and to prevent its value from being
submitted. The <code title="attr-fe-autofocus"><a href="association-of-controls-and-forms.html#attr-fe-autofocus">autofocus</a></code>
- attribute controls focus.</p><hr><p>If the element's <code title="attr-dir"><a href="elements.html#the-dir-attribute">dir</a></code> attribute is
- in the <i title="attr-dir-auto-state"><a href="elements.html#attr-dir-auto-state">auto</a></i> state, then for the
- purposes of the bidirectional algorithm, the user agent must <span class="XXX">act in a manner consistent with the CSS 'white-space:plaintext' feature<!-- see bug 11734 --></span>.
- This requirement may be implemented indirectly through the style
- layer. For example, an HTML+CSS user agent could implement these
- requirements by implementing the CSS 'unicode-bidi' property. <a href="references.html#refsCSS">[CSS]</a></p><hr><dl class="domintro"><dt><var title="">textarea</var> . <code title="attr-textarea-type">type</code></dt>
+ attribute controls focus.</p><dl class="domintro"><dt><var title="">textarea</var> . <code title="attr-textarea-type">type</code></dt>
<dd>
Index: dnd.html
===================================================================
RCS file: /sources/public/html5/spec/dnd.html,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- dnd.html 14 Feb 2011 23:51:09 -0000 1.43
+++ dnd.html 18 Feb 2011 08:46:56 -0000 1.44
@@ -419,8 +419,8 @@
series of <code title="event-mousemove">mousemove</code> events, and
the drop could be triggered by the mouse being released.</p><p>On media without a pointing device, the user would probably have
to explicitly indicate his intention to perform a drag-and-drop
- operation, stating what he wishes to drag and what he wishes to
- drop, respectively.</p><div class="impl">
+ operation, stating what he wishes to drag and where he wishes to
+ drop it, respectively.</p><div class="impl">
<p>However it is implemented, drag-and-drop operations must have a
starting point (e.g. where the mouse was clicked, or the start of
Index: links.html
===================================================================
RCS file: /sources/public/html5/spec/links.html,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -d -r1.48 -r1.49
--- links.html 14 Feb 2011 23:51:12 -0000 1.48
+++ links.html 18 Feb 2011 08:46:57 -0000 1.49
@@ -901,6 +901,13 @@
assume that the given icon is appropriate, but less appropriate than
an icon of a known and appropriate size.</p>
+ <p>In the absence of a <code><a href="semantics.html#the-link-element">link</a></code> with the <code title="rel-icon"><a href="#rel-icon">icon</a></code> keyword, for <code><a href="infrastructure.html#document">Document</a></code>s
+ obtained over HTTP or HTTPS, user agents may instead attempt to
+ <a href="fetching-resources.html#fetch">fetch</a> and use an icon with the <a href="urls.html#absolute-url">absolute
+ URL</a> obtained by resolving the <a href="urls.html#url">URL</a> "<code title="">/favicon.ico</code>" against <a href="dom.html#the-document-s-address">the document's
+ address</a>, as if the page had declared that icon using the
+ <code title="rel-icon"><a href="#rel-icon">icon</a></code> keyword.</p>
+
</div><div class="example">
<p>The following snippet shows the top part of an application with
@@ -1739,48 +1746,63 @@
<dd>
<p>The <code title="selector-active"><a href="#selector-active">:active</a></code> pseudo-class
- must match any element falling into one of the following
- categories between the time the user begins to activate the
- element and the time the user stops activating the element:</p>
+ is defined to match an element <q cite="http://dev.w3.org/csswg/selectors3/#the-user-action-pseudo-classes-hover-act">while
+ an element is <i>being activated</i> by the user</q>. For the
+ purposes of defining the <code title="selector-active"><a href="#selector-active">:active</a></code> pseudo-class only, an HTML
+ user agent must consider an element as <i>being activated</i> if
+ it is:</p>
- <ul><li><code><a href="text-level-semantics.html#the-a-element">a</a></code> elements that have an <code title="attr-hyperlink-href"><a href="#attr-hyperlink-href">href</a></code> attribute</li>
+ <ul><li>
- <li><code><a href="the-map-element.html#the-area-element">area</a></code> elements that have an <code title="attr-hyperlink-href"><a href="#attr-hyperlink-href">href</a></code> attribute</li>
+ <p>An element falling into one of the following categories
+ between the time the user begins to indicate an intent to
+ trigger the element's <a href="content-models.html#activation-behavior">activation behavior</a> and
+ either the time the user stops indicating an intent to trigger
+ the element's <a href="content-models.html#activation-behavior">activation behavior</a>, or the time the
+ element's <a href="content-models.html#activation-behavior">activation behavior</a> has finished running,
+ which ever comes first:</p>
- <li><code><a href="semantics.html#the-link-element">link</a></code> elements that have an <code title="attr-link-href"><a href="semantics.html#attr-link-href">href</a></code> attribute</li>
+ <ul><li><code><a href="text-level-semantics.html#the-a-element">a</a></code> elements that have an <code title="attr-hyperlink-href"><a href="#attr-hyperlink-href">href</a></code> attribute</li>
- <li><code><a href="the-button-element.html#the-button-element">button</a></code> elements that are not <a href="association-of-controls-and-forms.html#concept-fe-disabled" title="concept-fe-disabled">disabled</a></li>
+ <li><code><a href="the-map-element.html#the-area-element">area</a></code> elements that have an <code title="attr-hyperlink-href"><a href="#attr-hyperlink-href">href</a></code> attribute</li>
- <li><code><a href="the-input-element.html#the-input-element">input</a></code> elements whose <code title="attr-input-type"><a href="the-input-element.html#attr-input-type">type</a></code> attribute is in the <a href="number-state.html#submit-button-state" title="attr-input-type-submit">Submit Button</a>, <a href="number-state.html#image-button-state" title="attr-input-type-image">Image Button</a>, <a href="number-state.html#reset-button-state" title="attr-input-type-reset">Reset Button</a>, or <a href="number-state.html#button-state" title="attr-input-type-button">Button</a> state</li>
+ <li><code><a href="semantics.html#the-link-element">link</a></code> elements that have an <code title="attr-link-href"><a href="semantics.html#attr-link-href">href</a></code> attribute</li>
- <li><code><a href="interactive-elements.html#the-command">command</a></code> elements that do not have a <code title="attr-command-disabled"><a href="interactive-elements.html#attr-command-disabled">disabled</a></code> attribute</li>
+ <li><code><a href="the-button-element.html#the-button-element">button</a></code> elements that are not <a href="association-of-controls-and-forms.html#concept-fe-disabled" title="concept-fe-disabled">disabled</a></li>
- <li>elements that are <a href="editing.html#specially-focusable">specially focusable</a></li>
+ <li><code><a href="the-input-element.html#the-input-element">input</a></code> elements whose <code title="attr-input-type"><a href="the-input-element.html#attr-input-type">type</a></code> attribute is in the <a href="number-state.html#submit-button-state" title="attr-input-type-submit">Submit Button</a>, <a href="number-state.html#image-button-state" title="attr-input-type-image">Image Button</a>, <a href="number-state.html#reset-button-state" title="attr-input-type-reset">Reset Button</a>, or <a href="number-state.html#button-state" title="attr-input-type-button">Button</a> state</li>
- </ul><p class="example">For example, if the user is using a keyboard to
- push a <code><a href="the-button-element.html#the-button-element">button</a></code> element by pressing the space bar, the
- element would match this pseudo-class in between the time that the
- element received the <code title="event-keydown">keydown</code>
- event and the time the element received the <code title="event-keyup">keyup</code> event.</p>
+ <li><code><a href="interactive-elements.html#the-command">command</a></code> elements that do not have a <code title="attr-command-disabled"><a href="interactive-elements.html#attr-command-disabled">disabled</a></code> attribute</li>
- <p>In addition, the <code title="selector-active"><a href="#selector-active">:active</a></code>
- pseudo-class must match any element that the user indicates using
- a pointing device while that pointing device is in the "down"
- state (e.g. for a mouse, between the time the mouse button is
- pressed and the time it is depressed).</p>
+ <li>elements that are <a href="editing.html#specially-focusable">specially focusable</a></li>
- <p class="note">This requirement is a <a href="introduction.html#willful-violation">willful
- violation</a> of the Selectors specification (which only allows
- elements to match the <code title="selector-active"><a href="#selector-active">:active</a></code>
- pseudo-class when they are activated), motivated by a desire to be
- compatible with legacy user agents. <a href="references.html#refsSELECTORS">[SELECTORS]</a></p>
+ </ul><p class="example">For example, if the user is using a keyboard
+ to push a <code><a href="the-button-element.html#the-button-element">button</a></code> element by pressing the space bar,
+ the element would match this pseudo-class in between the time
+ that the element received the <code title="event-keydown">keydown</code> event and the time the
+ element received the <code title="event-keyup">keyup</code>
+ event.</p>
- <p>In addition, the <code title="selector-active"><a href="#selector-active">:active</a></code>
- pseudo-class must match any element that has an ancestor that
- matches the the <code title="selector-active"><a href="#selector-active">:active</a></code>
- pseudo-class.</p>
+ </li>
- </dd>
+ <li>
+
+ <p>An element that the user indicates using a pointing device
+ while that pointing device is in the "down" state (e.g. for a
+ mouse, between the time the mouse button is pressed and the time
+ it is depressed).</p>
+
+ </li>
+
+ <li>
+
+ <p>An element that has a descendant that is currently matching
+ the the <code title="selector-active"><a href="#selector-active">:active</a></code>
+ pseudo-class.</p>
+
+ </li>
+
+ </ul></dd>
<dt><dfn id="selector-enabled" title="selector-enabled"><code>:enabled</code></dfn></dt>
Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec/spec.html,v
retrieving revision 1.1385
retrieving revision 1.1386
diff -u -d -r1.1385 -r1.1386
--- spec.html 14 Feb 2011 23:51:12 -0000 1.1385
+++ spec.html 18 Feb 2011 08:47:03 -0000 1.1386
@@ -347,7 +347,7 @@
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id="editor-s-draft-14-february-2011">Editor's Draft 14 February 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-17-february-2011">Editor's Draft 17 February 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -369,7 +369,7 @@
<a href="Overview.html">single page HTML</a>,
<a href="spec.html">multipage HTML</a>,
<a href="author/">web developer edition</a>.
-This is revision 1.4728.
+This is revision 1.4744.
</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2010 <a href="http://www.w3.org/"><abbr title="World Wide
@@ -482,7 +482,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 14 February 2011 Editor's Draft.
+ This specification is the 17 February 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
Index: number-state.html
===================================================================
RCS file: /sources/public/html5/spec/number-state.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -d -r1.32 -r1.33
--- number-state.html 3 Feb 2011 20:57:40 -0000 1.32
+++ number-state.html 18 Feb 2011 08:46:57 -0000 1.33
@@ -1478,11 +1478,12 @@
this section apply.</p>
</div><p>The <code><a href="the-input-element.html#the-input-element">input</a></code> element <a href="rendering.html#represents">represents</a> a button
- with no default behavior. A label for the button must be provided
- in the <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute.
- <span class="impl">If the element has a <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, the button's label
- must be the value of that attribute; otherwise, it must be the empty
- string.</span> The element is a <a href="forms.html#concept-button" title="concept-button">button</a>.</p><div class="impl">
+ with no default behavior. A label for the button must be provided in
+ the <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, though it
+ may be the empty string. <span class="impl">If the element has a
+ <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, the button's
+ label must be the value of that attribute; otherwise, it must be the
+ empty string.</span> The element is a <a href="forms.html#concept-button" title="concept-button">button</a>.</p><div class="impl">
<p>If the element is <i title="concept-input-mutable"><a href="the-input-element.html#concept-input-mutable">mutable</a></i>,
the user agent should allow the user to activate the element. The
Index: webappapis.html
===================================================================
RCS file: /sources/public/html5/spec/webappapis.html,v
retrieving revision 1.154
retrieving revision 1.155
diff -u -d -r1.154 -r1.155
--- webappapis.html 14 Feb 2011 23:51:16 -0000 1.154
+++ webappapis.html 18 Feb 2011 08:47:17 -0000 1.155
@@ -1164,7 +1164,9 @@
<code>MessagePort</code> objects.</p>
<hr></div><p><dfn id="event-handler-content-attributes">Event handler content attributes</dfn>, when specified, must
- contain valid JavaScript code matching the <code title="">FunctionBody</code> production. <a href="references.html#refsECMA262">[ECMA262]</a></p><div class="impl">
+ contain valid JavaScript code which, when parsed, would match the
+ <code title="">FunctionBody</code> production after automatic
+ semicolon insertion. <a href="references.html#refsECMA262">[ECMA262]</a></p><div class="impl">
<!-- SCRIPT EXEC -->
<p>When an <a href="#event-handler-content-attributes" title="event handler content attributes">event
Index: common-microsyntaxes.html
===================================================================
RCS file: /sources/public/html5/spec/common-microsyntaxes.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -d -r1.34 -r1.35
--- common-microsyntaxes.html 14 Feb 2011 23:51:08 -0000 1.34
+++ common-microsyntaxes.html 18 Feb 2011 08:46:48 -0000 1.35
@@ -1655,9 +1655,9 @@
date and time string</a> representing <var title="">datetime</var>, with the <a href="#valid-time-string">valid time string</a>
component being given in its shortest possible form, with the last
character of the string not being a U+005A LATIN CAPITAL LETTER Z
- character (Z), even if the time zone is UTC, and with a U+002D
- HYPHEN-MINUS character (-) representing the sign of the time-zone
- offset when the time zone is UTC.</p>
+ character (Z), even if the time zone is UTC, and with a U+002B PLUS
+ SIGN character (+) representing the sign of the time-zone offset
+ when the time zone is UTC.</p>
<p>The rules to <dfn id="parse-a-global-date-and-time-string">parse a global date and time string</dfn> are
as follows. This will return either a time in UTC, with associated
Received on Friday, 18 February 2011 08:47:26 UTC