[html5] r3302 - [] (0) Variety of editorial cleanup; also, fix the Action facet of <input> controls.
whatwg at whatwg.org
whatwg at whatwg.org
Wed Jun 17 00:01:56 PDT 2009
Author: ianh
Date: 2009-06-17 00:01:54 -0700 (Wed, 17 Jun 2009)
New Revision: 3302
Modified:
index
source
Log:
[] (0) Variety of editorial cleanup; also, fix the Action facet of <input> controls.
Modified: index
===================================================================
--- index 2009-06-17 06:17:40 UTC (rev 3301)
+++ index 2009-06-17 07:01:54 UTC (rev 3302)
@@ -39262,8 +39262,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
@@ -39301,9 +39301,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>
@@ -39591,15 +39593,11 @@
<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>
- <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).</p>
+ <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.</p>
@@ -41154,18 +41152,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=#refsE163>[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
@@ -45296,8 +45282,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>;
@@ -45383,11 +45369,12 @@
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
- -->
+<!-- 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>
@@ -47117,7 +47104,7 @@
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?</p>
+ <!-- v2: we should probably support HTML4's Content-Script-Type header here. -->
<div class=impl>
@@ -47239,10 +47226,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 -->
@@ -47291,7 +47278,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 -->
@@ -47305,22 +47292,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=#refsDOM3EVENTS>[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
@@ -47341,13 +47320,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>
@@ -48113,10 +48085,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>
@@ -48128,9 +48100,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 - ->
@@ -70066,6 +70038,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
@@ -70092,6 +70065,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
-->
Modified: source
===================================================================
--- source 2009-06-17 06:17:40 UTC (rev 3301)
+++ source 2009-06-17 07:01:54 UTC (rev 3302)
@@ -44109,8 +44109,8 @@
<p>If the <span title="command-facet-Type">Type</span> is "command",
then it is the string given by the <code
title="attr-input-value">value</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 <span title="command-facet-Type">Type</span> is
"radio" or "checkbox". If the element is a <span>labeled
@@ -44155,10 +44155,11 @@
attribute, and false otherwise.</p>
<p>The <span title="command-facet-Action">Action</span> of the
- command is to <span title="fire a click event">fire a <code
- title="event-click">click</code> event</span> 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 <span>activation
+ behavior</span>, is to <span>run synthetic click activation
+ steps</span> on the element. Otherwise, it is just to <span>fire a
+ <code title="event-click">click</code> event</span> at the
+ element.</p>
<h5><dfn title="option-command">Using the <code>option</code> element to define a command</dfn></h5>
@@ -44498,15 +44499,11 @@
title="attr-title">title</code> attributes to mark up semantics
common to a group of consecutive elements.</p>
- <p class="XXX">Allowing <code>div</code> elements to contain
- phrasing content makes it easy for authors to abuse
- <code>div</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>div</code>s as the extension mechanism that
- they are, to handle things the spec can't otherwise do (like making
- new widgets).</p>
+ <p class="note">Authors are strongly encouraged to view the
+ <code>div</code> element as an element of last resort, for when no
+ other element is suitable. Use of the <code>div</code> element
+ instead of more appropriate elements leads to poor accessibility for
+ readers and poor maintainability for authors.</p>
@@ -46391,18 +46388,6 @@
<code title="md-vcard-tel-value">value</code> property. <a
href="#refsE163">[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">type</code> properties
are present within an <span title="concept-item">item</span> that
forms the <span title="concept-property-value">value</span> of a
@@ -51534,8 +51519,8 @@
<span>WindowProxy</span> <span title="dom-open">open</span>([Optional] in DOMString url, [Optional] in DOMString target, [Optional] in DOMString features, [Optional] in DOMString replace);
// the user agent
- readonly attribute <span>Navigator</span> <span title="dom-navigator">navigator</span>; <!-- 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 <span>Navigator</span> <span title="dom-navigator">navigator</span>; <!-- 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 <span>ApplicationCache</span> <span title="dom-applicationCache">applicationCache</span>;
@@ -51621,11 +51606,12 @@
attribute <span>Function</span> <span title="handler-onwaiting">onwaiting</span>;
};</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
- -->
+<!-- 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">
@@ -53635,7 +53621,7 @@
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?</p>
+ <!-- v2: we should probably support HTML4's Content-Script-Type header here. -->
<div class="impl">
@@ -53778,10 +53764,10 @@
<tr><td><dfn title="handler-onprogress"><code>onprogress</code></dfn> <td> <code title="event-progress">progress</code>
<tr><td><dfn title="handler-onratechange"><code>onratechange</code></dfn> <td> <code title="event-ratechange">ratechange</code>
<tr><td><dfn title="handler-onreadystatechange"><code>onreadystatechange</code></dfn> <td> <code title="event-readystatechange">readystatechange</code>
- <tr><td><dfn 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 title="handler-onscroll"><code>onscroll</code></dfn> <td> <code title="event-scroll">scroll</code> <!-- widely used --> <!-- [CSSOM] -->
<tr><td><dfn title="handler-onseeked"><code>onseeked</code></dfn> <td> <code title="event-seeked">seeked</code>
<tr><td><dfn title="handler-onseeking"><code>onseeking</code></dfn> <td> <code title="event-seeking">seeking</code>
- <tr><td><dfn 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 title="handler-onselect"><code>onselect</code></dfn> <td> <code title="event-select">select</code> <!-- widely used --> <!-- [CSSOM] -->
<tr><td><dfn title="handler-onshow"><code>onshow</code></dfn> <td> <code title="event-show">show</code>
<tr><td><dfn title="handler-onstalled"><code>onstalled</code></dfn> <td> <code title="event-stalled">stalled</code>
<tr><td><dfn title="handler-onsubmit"><code>onsubmit</code></dfn> <td> <code title="event-submit">submit</code> <!-- widely used -->
@@ -53844,7 +53830,7 @@
<tr><td><dfn title="handler-window-ononline"><code>ononline</code></dfn> <td> <code title="event-online">online</code> <!-- new -->
<tr><td><dfn title="handler-window-onpopstate"><code>onpopstate</code></dfn> <td> <code title="event-popstate">popstate</code> <!-- new -->
<tr><td><dfn title="handler-window-onredo"><code>onredo</code></dfn> <td> <code title="event-redo">redo</code> <!-- new -->
- <tr><td><dfn 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 title="handler-window-onresize"><code>onresize</code></dfn> <td> <code title="event-resize">resize</code> <!-- widely used --> <!-- [CSSOM] -->
<tr><td><dfn title="handler-window-onstorage"><code>onstorage</code></dfn> <td> <code title="event-storage">storage</code> <!-- new -->
<tr><td><dfn title="handler-window-onundo"><code>onundo</code></dfn> <td> <code title="event-undo">undo</code> <!-- new -->
<tr><td><dfn title="handler-window-onunload"><code>onunload</code></dfn> <td> <code title="event-unload">unload</code> <!-- widely used -->
@@ -53861,13 +53847,6 @@
<h5>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">click()</code>
method on the <code>HTMLElement</code> interface is defined as
@@ -53875,10 +53854,9 @@
element. <a href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
<p><dfn 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
+ 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
@@ -53909,13 +53887,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>
@@ -54817,10 +54788,10 @@
void <span title="dom-navigator-registerProtocolHandler">registerProtocolHandler</span>(in DOMString scheme, in DOMString url, in DOMString title);
void <span title="dom-navigator-registerContentHandler">registerContentHandler</span>(in DOMString mimeType, in DOMString url, in DOMString title);
void <span title="dom-navigator-getStorageUpdates">getStorageUpdates</span>();
-<!-- 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">
@@ -54832,9 +54803,9 @@
defined separately so that other specifications can re-use parts of
the <code>Navigator</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 - ->
@@ -82640,6 +82611,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
@@ -82666,6 +82638,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
-->
More information about the Commit-Watchers
mailing list