- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 17 Jun 2009 07:02:02 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv10596
Modified Files:
Overview.html
Log Message:
Variety of editorial cleanup; also, fix the Action facet of <input> controls. (whatwg r3302)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2447
retrieving revision 1.2448
diff -u -d -r1.2447 -r1.2448
--- Overview.html 17 Jun 2009 06:17:46 -0000 1.2447
+++ Overview.html 17 Jun 2009 07:01:59 -0000 1.2448
@@ -34913,8 +34913,8 @@
<p>If the <a href="#command-facet-type" title="command-facet-Type">Type</a> is "command",
then it is the string given by the <code title="attr-input-value"><a href="#attr-input-value">value</a></code> attribute, if any, and a
- <span>UA-dependent value</span><!-- XXX xref--> that the UA uses to
- label the button itself if the attribute is absent.</p>
+ UA-dependent, locale-dependent value that the UA uses to label the
+ button itself if the attribute is absent.</p>
<p>Otherwise, the <a href="#command-facet-type" title="command-facet-Type">Type</a> is
"radio" or "checkbox". If the element is a <a href="#labeled-control">labeled
@@ -34952,9 +34952,11 @@
attribute, and false otherwise.</p>
<p>The <a href="#command-facet-action" title="command-facet-Action">Action</a> of the
- command is to <a href="#fire-a-click-event" title="fire a click event">fire a <code title="event-click">click</code> event</a> at the element.</p> <!-- XXX this
- is probably wrong for radio and checkbox types, depending on how we
- define <input>. -->
+ command, if the element has a defined <a href="#activation-behavior">activation
+ behavior</a>, is to <a href="#run-synthetic-click-activation-steps">run synthetic click activation
+ steps</a> on the element. Otherwise, it is just to <a href="#fire-a-click-event">fire a
+ <code title="event-click">click</code> event</a> at the
+ element.</p>
<h5 id="using-the-option-element-to-define-a-command"><span class="secno">4.11.6.4 </span><dfn title="option-command">Using the <code>option</code> element to define a command</dfn></h5>
@@ -35226,15 +35228,11 @@
<dd>Uses <code><a href="#htmlelement">HTMLElement</a></code>.</dd>
</dl><p>The <code><a href="#the-div-element">div</a></code> element has no special meaning at all. It
<a href="#represents">represents</a> its children. It can be used with the <code title="attr-class"><a href="#classes">class</a></code>, <code title="attr-lang"><a href="#attr-lang">lang</a></code>, and <code title="attr-title"><a href="#the-title-attribute">title</a></code> attributes to mark up semantics
- common to a group of consecutive elements.<p class="XXX">Allowing <code><a href="#the-div-element">div</a></code> elements to contain
- phrasing content makes it easy for authors to abuse
- <code><a href="#the-div-element">div</a></code>, using it with the <code>class=""</code> attribute
- to the point of not having any other elements in the markup. This is
- a disaster from an accessibility point of view, and it would be nice
- if we could somehow make such pages non-compliant without preventing
- people from using <code><a href="#the-div-element">div</a></code>s as the extension mechanism that
- they are, to handle things the spec can't otherwise do (like making
- new widgets).<div class="impl">
+ common to a group of consecutive elements.<p class="note">Authors are strongly encouraged to view the
+ <code><a href="#the-div-element">div</a></code> element as an element of last resort, for when no
+ other element is suitable. Use of the <code><a href="#the-div-element">div</a></code> element
+ instead of more appropriate elements leads to poor accessibility for
+ readers and poor maintainability for authors.<div class="impl">
<h3 id="matching-html-elements-using-selectors"><span class="secno">4.13 </span>Matching HTML elements using selectors</h3>
@@ -36592,18 +36590,6 @@
defined in the CCITT specifications E.163 and X.121, or an <a href="#concept-item" title="concept-item">item</a> with zero or more <code title="md-vcard-tel-type"><a href="#md-vcard-tel-type">type</a></code> properties and exactly one
<code title="md-vcard-tel-value"><a href="#md-vcard-tel-value">value</a></code> property. <a href="#references">[E.163]</a> <a href="#X.121">[X.121]</a></p>
- <!-- XXX refs
-
- [E.163] Recommendation E.163 - Numbering Plan for The
- International Telephone Service, CCITT Blue Book,
- Fascicle II.2, pp. 128-134, November, 1988.
-
- [X.121] Recommendation X.121 - International Numbering Plan for
- Public Data Networks, CCITT Blue Book, Fascicle VIII.3,
- pp. 317-332, November, 1988.
-
- -->
-
<p>If no <code title="md-vcard-tel-type"><a href="#md-vcard-tel-type">type</a></code> properties
are present within an <a href="#concept-item" title="concept-item">item</a> that
forms the <a href="#concept-property-value" title="concept-property-value">value</a> of a
@@ -40516,8 +40502,8 @@
<a href="#windowproxy">WindowProxy</a> <a href="#dom-open" title="dom-open">open</a>([Optional] in DOMString url, [Optional] in DOMString target, [Optional] in DOMString features, [Optional] in DOMString replace);
// the user agent
- readonly attribute <a href="#navigator">Navigator</a> <a href="#dom-navigator" title="dom-navigator">navigator</a>; <!-- XXX IE6 also has window.clientInformation pointing to this same object -->
- readonly attribute <span>Storage</span> <span title="dom-localStorage">localStorage</span>; <!-- XXX split into separate interface -->
+ readonly attribute <a href="#navigator">Navigator</a> <a href="#dom-navigator" title="dom-navigator">navigator</a>; <!-- IE also has window.clientInformation === window.navigator -->
+ readonly attribute <span>Storage</span> <span title="dom-localStorage">localStorage</span>;
readonly attribute <span>Storage</span> <span title="dom-sessionStorage">sessionStorage</span>;
<span>Database</span> <span title="dom-opendatabase">openDatabase</span>(in DOMString name, in DOMString version, in DOMString displayName, in unsigned long estimatedSize);
readonly attribute <a href="#applicationcache">ApplicationCache</a> <a href="#dom-applicationcache" title="dom-applicationCache">applicationCache</a>;
@@ -40601,11 +40587,12 @@
attribute <a href="#function">Function</a> <a href="#handler-window-onunload" title="handler-window-onunload">onunload</a>;
attribute <a href="#function">Function</a> <a href="#handler-onvolumechange" title="handler-onvolumechange">onvolumechange</a>;
attribute <a href="#function">Function</a> <a href="#handler-onwaiting" title="handler-onwaiting">onwaiting</a>;
-};</pre><!-- XXX http://msdn.microsoft.com/workshop/author/dhtml/reference/objects/obj_window.asp
- http://www.mozilla.org/docs/dom/domref/dom_window_ref.html
- http://lxr.mozilla.org/mozilla/source/dom/public/idl/base/nsIDOMWindow.idl - scrollBy, etc
- http://lxr.mozilla.org/mozilla/source/dom/public/idl/base/nsIDOMWindowInternal.idl - DOM level 0
- --><dl class="domintro"><dt><var title="">window</var> . <code title="dom-window"><a href="#dom-window">window</a></code></dt>
+};</pre><!-- for more features to add here, look here:
+ http://msdn.microsoft.com/workshop/author/dhtml/reference/objects/obj_window.asp
+ http://www.mozilla.org/docs/dom/domref/dom_window_ref.html
+ http://lxr.mozilla.org/mozilla/source/dom/public/idl/base/nsIDOMWindow.idl - scrollBy, etc
+ http://lxr.mozilla.org/mozilla/source/dom/public/idl/base/nsIDOMWindowInternal.idl - DOM level 0
+--><dl class="domintro"><dt><var title="">window</var> . <code title="dom-window"><a href="#dom-window">window</a></code></dt>
<dt><var title="">window</var> . <code title="dom-frames"><a href="#dom-frames">frames</a></code></dt>
<dt><var title="">window</var> . <code title="dom-self"><a href="#dom-self">self</a></code></dt>
@@ -42226,7 +42213,7 @@
the corresponding <a href="#event-handler-attributes-0" title="event handler attributes">event
handler attribute</a>.</p><!--
http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...%3Cbody%20onload%3D%22w(%27pass%27)%22%3E%0A%3Cscript%3Edocument.body.removeAttribute(%27onload%27)%3B%3C%2Fscript%3E
- --><p class="XXX">How do we allow non-JS event handlers?<div class="impl">
+ --><!-- v2: we should probably support HTML4's Content-Script-Type header here. --><div class="impl">
<hr><p>All <a href="#event-handler-attributes-0">event handler attributes</a> on an element, whether
set to null or to a <code><a href="#function">Function</a></code> object, must be registered
@@ -42343,10 +42330,10 @@
<tr><td><dfn id="handler-onprogress" title="handler-onprogress"><code>onprogress</code></dfn> <td> <code title="event-progress"><a href="#event-progress">progress</a></code>
<tr><td><dfn id="handler-onratechange" title="handler-onratechange"><code>onratechange</code></dfn> <td> <code title="event-ratechange"><a href="#event-ratechange">ratechange</a></code>
<tr><td><dfn id="handler-onreadystatechange" title="handler-onreadystatechange"><code>onreadystatechange</code></dfn> <td> <code title="event-readystatechange">readystatechange</code>
- <tr><td><dfn id="handler-onscroll" title="handler-onscroll"><code>onscroll</code></dfn> <td> <code title="event-scroll">scroll</code> <!-- widely used --> <!-- XXX should define when it fires -->
+ <tr><td><dfn id="handler-onscroll" title="handler-onscroll"><code>onscroll</code></dfn> <td> <code title="event-scroll">scroll</code> <!-- widely used --> <!-- [CSSOM] -->
<tr><td><dfn id="handler-onseeked" title="handler-onseeked"><code>onseeked</code></dfn> <td> <code title="event-seeked"><a href="#event-seeked">seeked</a></code>
<tr><td><dfn id="handler-onseeking" title="handler-onseeking"><code>onseeking</code></dfn> <td> <code title="event-seeking"><a href="#event-seeking">seeking</a></code>
- <tr><td><dfn id="handler-onselect" title="handler-onselect"><code>onselect</code></dfn> <td> <code title="event-select">select</code> <!-- widely used --> <!-- XXX should define when it fires -->
+ <tr><td><dfn id="handler-onselect" title="handler-onselect"><code>onselect</code></dfn> <td> <code title="event-select">select</code> <!-- widely used --> <!-- [CSSOM] -->
<tr><td><dfn id="handler-onshow" title="handler-onshow"><code>onshow</code></dfn> <td> <code title="event-show">show</code>
<tr><td><dfn id="handler-onstalled" title="handler-onstalled"><code>onstalled</code></dfn> <td> <code title="event-stalled"><a href="#event-stalled">stalled</a></code>
<tr><td><dfn id="handler-onsubmit" title="handler-onsubmit"><code>onsubmit</code></dfn> <td> <code title="event-submit">submit</code> <!-- widely used -->
@@ -42395,7 +42382,7 @@
<tr><td><dfn id="handler-window-ononline" title="handler-window-ononline"><code>ononline</code></dfn> <td> <code title="event-online"><a href="#event-online">online</a></code> <!-- new -->
<tr><td><dfn id="handler-window-onpopstate" title="handler-window-onpopstate"><code>onpopstate</code></dfn> <td> <code title="event-popstate"><a href="#event-popstate">popstate</a></code> <!-- new -->
<tr><td><dfn id="handler-window-onredo" title="handler-window-onredo"><code>onredo</code></dfn> <td> <code title="event-redo"><a href="#event-redo">redo</a></code> <!-- new -->
- <tr><td><dfn id="handler-window-onresize" title="handler-window-onresize"><code>onresize</code></dfn> <td> <code title="event-resize">resize</code> <!-- widely used --> <!-- XXX should define when it fires -->
+ <tr><td><dfn id="handler-window-onresize" title="handler-window-onresize"><code>onresize</code></dfn> <td> <code title="event-resize">resize</code> <!-- widely used --> <!-- [CSSOM] -->
<tr><td><dfn id="handler-window-onstorage" title="handler-window-onstorage"><code>onstorage</code></dfn> <td> <code title="event-storage">storage</code> <!-- new -->
<tr><td><dfn id="handler-window-onundo" title="handler-window-onundo"><code>onundo</code></dfn> <td> <code title="event-undo"><a href="#event-undo">undo</a></code> <!-- new -->
<tr><td><dfn id="handler-window-onunload" title="handler-window-onunload"><code>onunload</code></dfn> <td> <code title="event-unload">unload</code> <!-- widely used -->
@@ -42406,22 +42393,14 @@
<h5 id="event-firing"><span class="secno">6.5.6.3 </span>Event firing</h5>
- <p class="XXX">maybe this should be moved higher up
- (terminology? conformance? DOM?) Also, the whole terminology thing
- should be changed so that we don't define any specific events here,
- we only define 'simple event', 'progress event', 'mouse event', 'key
- event', and the like, and have the actual dispatch use those generic
- terms when firing events.</p>
-
<p>Certain operations and methods are defined as firing events on
elements. For example, the <code title="dom-click"><a href="#dom-click">click()</a></code>
method on the <code><a href="#htmlelement">HTMLElement</a></code> interface is defined as
firing a <code title="event-click">click</code> event on the
element. <a href="#references">[DOM3EVENTS]</a></p>
- <p><dfn id="fire-a-click-event" title="fire a click event">Firing a <code title="event-click">click</code> event</dfn> means that a <a href="http://www.w3.org/TR/DOM-Level-3-Events/events.html#event-click"><code>click</code></a>
- event with no
- namespace, which bubbles and is cancelable, and which uses the
+ <p><dfn id="fire-a-click-event" title="fire a click event">Firing a <code title="event-click">click</code> event</dfn> means that a <code title="event-click">click</code> event with no namespace, which
+ bubbles and is cancelable, and which uses the
<code>MouseEvent</code> interface, must be dispatched at the given
target. The event object must have its <code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes set to 0, its <code title="">ctrlKey</code>, <code title="">shiftKey</code>, <code title="">altKey</code>, and <code title="">metaKey</code> attributes
set according to the current state of the key input device, if any
@@ -42442,13 +42421,6 @@
<p>The default action of these event is to do nothing unless
otherwise stated.</p>
- <p class="XXX">If you dispatch a custom "click" event at an
- element that would normally have default actions, should they get
- triggered? If so, we need to go through the entire spec and make
- sure that any default actions are defined in terms of <em>any</em>
- event of the right type on that element, not those that are
- dispatched in expected ways.</p>
-
</div><div class="impl">
<h5 id="events-and-the-window-object"><span class="secno">6.5.6.4 </span>Events and the <code><a href="#window">Window</a></code> object</h5>
@@ -43161,10 +43133,10 @@
void <a href="#dom-navigator-registerprotocolhandler" title="dom-navigator-registerProtocolHandler">registerProtocolHandler</a>(in DOMString scheme, in DOMString url, in DOMString title);
void <a href="#dom-navigator-registercontenthandler" title="dom-navigator-registerContentHandler">registerContentHandler</a>(in DOMString mimeType, in DOMString url, in DOMString title);
void <a href="#dom-navigator-getstorageupdates" title="dom-navigator-getStorageUpdates">getStorageUpdates</a>();
-<!-- XXX cookieEnabled geolocator javaEnabled mozIsLocallyAvailable preference
+<!-- v2: cookieEnabled geolocator javaEnabled mozIsLocallyAvailable preference
readonly attribute <span>MimeTypeArray</span> <span title="dom-navigator-mimeTypes">mimeTypes</span>;
readonly attribute <span>PluginArray</span> <span title="dom-navigator-plugins">plugins</span>;
- (the latter is used in a <video> element demo now)
+ (the latter is used in a <video> element demo now, so we might need to pull this forward from v2!)
-->};</pre><div class="impl">
<p>Objects implementing the <code><a href="#navigator">Navigator</a></code> interface must
@@ -43174,9 +43146,9 @@
defined separately so that other specifications can re-use parts of
the <code><a href="#navigator">Navigator</a></code> interface.)</p>
- <!-- XXX also, see window.external.AddSearchProvider() and similar DOM APIs from IE -->
+ <!-- v2: also, see window.external.AddSearchProvider() and similar DOM APIs from IE -->
- <!-- XXX also, could expose languages:
+ <!-- v2: also, could expose languages:
<dt><dfn title="dom-navigator-browserLanguage"><code>browserLanguage</code></dfn></dt> <!- - Opera and IE only - ->
<dd><p>Must return either null or a language code representing the language the browser uses in its interface.</p></dd>
<dt><dfn title="dom-navigator-userLanguage"><code>userLanguage</code></dfn></dt> <!- - Opera and IE only - ->
@@ -63827,6 +63799,7 @@
[CSSOM] CSS Object Model
[CSSUI] CSS3 UI
[CSSWEBFONTS] CSS3 Web Fonts
+ [E.163] Recommendation E.163 - Numbering Plan for The International Telephone Service, CCITT Blue Book, Fascicle II.2, pp. 128-134, November, 1988.
[EUCKR] Korea Industrial Standards Association, "Hangul Unix Environment," Korean Industrial Standard, 1992, Ref. No. KS C 5861-1992.
[GBK] http://www.iana.org/assignments/charset-reg/GBK
@@ -63853,6 +63826,7 @@
[WIN874] http://www.microsoft.com/globaldev/reference/sbcs/874.mspx
[WIN874] http://www.microsoft.com/globaldev/reference/sbcs/874.mspx OR http://msdn.microsoft.com/en-us/goglobal/cc305142.aspx
[WIN949] http://www.microsoft.com/globaldev/reference/dbcs/949.mspx OR http://msdn.microsoft.com/en-us/goglobal/cc305154.aspx
+ [X.121] Recommendation X.121 - International Numbering Plan for Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332, November, 1988.
[X690] http://www.itu.int/ITU-T/studygroups/com17/languages/X.690-0207.pdf
--><h2 class="no-num" id="acknowledgements">Acknowledgements</h2><!-- ACKS --><p>Thanks to
Received on Wednesday, 17 June 2009 07:02:10 UTC