[html5] r3567 - [e] (0) Clean up some references in preparation for actually having a references [...]
whatwg at whatwg.org
whatwg at whatwg.org
Sat Aug 8 01:20:05 PDT 2009
Author: ianh
Date: 2009-08-08 01:20:04 -0700 (Sat, 08 Aug 2009)
New Revision: 3567
Modified:
index
source
Log:
[e] (0) Clean up some references in preparation for actually having a references section.
Modified: index
===================================================================
--- index 2009-08-08 07:58:40 UTC (rev 3566)
+++ index 2009-08-08 08:20:04 UTC (rev 3567)
@@ -1675,7 +1675,7 @@
<p>The term <dfn id=text-node>text node</dfn> refers to any <code>Text</code>
node, including <code>CDATASection</code> nodes; specifically, any
<code>Node</code> with node type <code title="">TEXT_NODE</code> (3)
- or <code title="">CDATA_SECTION_NODE</code> (4). <a href=#refsDOM3CORE>[DOM3CORE]</a></p>
+ or <code title="">CDATA_SECTION_NODE</code> (4). <a href=#refsDOMCORE>[DOMCORE]</a></p>
<p>A content attribute is said to <dfn title="">change</dfn> value
only if its new value is different than its previous value; setting
@@ -1701,7 +1701,7 @@
<p>The terms <dfn title="">fire</dfn> and <dfn title="">dispatch</dfn> are used
interchangeably in the context of events, as in the DOM Events
- specifications. <a href=#refsDOM3EVENTS>[DOM3EVENTS]</a></p>
+ specifications. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
<h4 id=plugins><span class=secno>2.1.4 </span>Plugins</h4>
@@ -2100,12 +2100,12 @@
model — of a document and its content. The DOM is not just
an API; the conformance criteria of HTML implementations are
defined, in this specification, in terms of operations on the DOM.
- <a href=#refsDOM3CORE>[DOM3CORE]</a></p>
+ <a href=#refsDOMCORE>[DOMCORE]</a></p>
<p>Implementations must support some version of DOM Core and DOM
Events, because this specification is defined in terms of the DOM,
and some of the features are defined as extensions to the DOM Core
- interfaces. <a href=#refsDOM3CORE>[DOM3CORE]</a> <a href=#refsDOM3CORE>[DOM3EVENTS]</a></p>
+ interfaces. <a href=#refsDOMCORE>[DOMCORE]</a> <a href=#refsDOMCORE>[DOMEVENTS]</a></p>
</dd>
@@ -6406,7 +6406,7 @@
<p>DOM3 Core defines mechanisms for checking for interface support,
and for obtaining implementations of interfaces, using <a href=http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMFeatures>feature
- strings</a>. <a href=#refsDOM3CORE>[DOM3CORE]</a></p>
+ strings</a>. <a href=#refsDOMCORE>[DOMCORE]</a></p>
<p>Authors are strongly discouraged from using these, as they are
notoriously unreliable and imprecise. Authors are encouraged to rely
@@ -6488,7 +6488,7 @@
<h3 id=documents><span class=secno>3.2 </span>Documents</h3>
<p>Every XML and HTML document in an HTML UA is represented by a
- <code>Document</code> object. <a href=#refsDOM3CORE>[DOM3CORE]</a></p>
+ <code>Document</code> object. <a href=#refsDOMCORE>[DOMCORE]</a></p>
<p><dfn id="the-document's-address">The document's address</dfn> is an <a href=#absolute-url>absolute URL</a>
that is set when the <code>Document</code> is created. <dfn id="the-document's-current-address">The
@@ -6746,7 +6746,7 @@
it would include if <a href=#fetch title=fetch>fetching</a> the resource
indicated by <a href="#the-document's-address">the document's address</a> over HTTP, as per
RFC 2109 section 4.3.4 or later specifications, excluding HTTP-only
- cookies. <a href=#refsRFC2109>[RFC2109]</a> <a href=#refsRFC2965>[RFC2965]</a></p>
+ cookies. <a href=#refsRFC2109>[RFC2109]</a> <a href=#refsCOOKIES>[COOKIES]</a></p>
<p>On setting, if the document is not associated with a
<a href=#browsing-context>browsing context</a> then the user agent must raise an
@@ -6763,7 +6763,7 @@
response with a <code>Set-Cookie</code> header whose value was the
specified value, as per RFC 2109 sections 4.3.1, 4.3.2, and 4.3.3 or
later specifications, but without overwriting the values of
- HTTP-only cookies. <a href=#refsRFC2109>[RFC2109]</a> <a href=#refsRFC2965>[RFC2965]</a></p>
+ HTTP-only cookies. <a href=#refsRFC2109>[RFC2109]</a> <a href=#refsCOOKIES>[COOKIES]</a></p>
<p class=note>This specification does not define what makes an
HTTP-only cookie, and at the time of publication the editor is not
@@ -8915,9 +8915,9 @@
<p>For <a href=#html-documents>HTML documents</a>, and for <a href=#html-elements>HTML
elements</a> in <a href=#html-documents>HTML documents</a>, certain APIs defined
- in DOM3 Core become case-insensitive or case-changing, as sometimes
- defined in DOM3 Core, and as summarized <span class=impl>or
- required</span> below. <a href=#refsDOM3CORE>[DOM3CORE]</a>.</p>
+ in DOM Core become case-insensitive or case-changing, as sometimes
+ defined in DOM Core, and as summarized <span class=impl>or
+ required</span> below. <a href=#refsDOMCORE>[DOMCORE]</a>.</p>
<p>This does not apply to <a href=#xml-documents>XML documents</a> or to elements
that are not in the <a href=#html-namespace-0>HTML namespace</a> despite being in
@@ -10287,7 +10287,7 @@
the order that they were given in the HTTP entity header. (URIs in
these headers are to be processed and resolved according to the
rules given in HTTP; the rules of <em>this</em> specification don't
- apply.) <a href=#refsHTTP>[HTTP]</a> <a href=#refsRFC2068>[RFC2068]</a></p>
+ apply.) <a href=#refsHTTP>[HTTP]</a> <a href=#refsWEBLINK>[WEBLINK]</a></p> <!-- WEBLINK is ref for Link: header -->
<p>The DOM attributes <dfn id=dom-link-href title=dom-link-href><code>href</code></dfn>, <dfn id=dom-link-rel title=dom-link-rel><code>rel</code></dfn>, <dfn id=dom-link-media title=dom-link-media><code>media</code></dfn>, <dfn id=dom-link-hreflang title=dom-link-hreflang><code>hreflang</code></dfn>, and <dfn id=dom-link-type title=dom-link-type><code>type</code></dfn>, and <dfn id=dom-link-sizes title=dom-link-sizes><code>sizes</code></dfn> each must
<a href=#reflect>reflect</a> the respective content attributes of the same
@@ -16315,7 +16315,7 @@
<p>Mathematical expressions often use subscripts and superscripts.
Authors are encouraged to use MathML for marking up mathematics, but
authors may opt to use <code><a href=#the-sub-and-sup-elements>sub</a></code> and <code><a href=#the-sub-and-sup-elements>sup</a></code> if
- detailed mathematical markup is not desired. <a href=#refsMathML>[MathML]</a></p>
+ detailed mathematical markup is not desired. <a href=#refsMATHML>[MATHML]</a></p>
<div class=example>
<pre><var>E</var>=<var>m</var><var>c</var><sup>2</sup></pre>
@@ -25416,7 +25416,7 @@
clamped to zero. If the result is more than 255, it must be clamped
to 255. If the number is not an integer, it should be rounded to the
nearest integer using the IEEE 754r
- <i>convertToIntegerTiesToEven</i> rounding mode. <a href=#refsECMA262>[ECMA262]</a> <a href=#refsIEEE754r>[IEEE754R]</a></p>
+ <i>convertToIntegerTiesToEven</i> rounding mode. <a href=#refsECMA262>[ECMA262]</a> <a href=#refsIEEE754R>[IEEE754R]</a></p>
<p class=note>The width and height (<var title="">w</var> and <var title="">h</var>) might be different from the <var title="">sw</var>
and <var title="">sh</var> arguments to the above methods, e.g. if
@@ -39822,7 +39822,7 @@
title="">index</var>th row in the selection. If the argument is out
of range (less than zero or greater than the number of selected rows
minus one), then it must raise an <code>INDEX_SIZE_ERR</code>
- exception. <a href="#refsDOM3CORE">[DOM3CORE]</a></p>
+ exception. <a href="#refsDOMCORE">[DOMCORE]</a></p>
<p>The <dfn
title="dom-DataGridSelection-isSelected"><code>isSelected()</code></dfn>
@@ -45912,7 +45912,7 @@
media used for the presentation of a particular
<code>Document</code> object in some media. A view may be
interactive. Each view is represented by an
- <code>AbstractView</code> object. <a href=#refsDOM2VIEWS>[DOM2VIEWS]</a></p>
+ <code>AbstractView</code> object. <a href=#refsDOMVIEWS>[DOMVIEWS]</a></p>
<p>The main <a href=#view>view</a> through which a user primarily
interacts with a user agent is the <dfn id=default-view>default view</dfn>. The
@@ -45929,14 +45929,14 @@
<code>DocumentView</code> interface must return the <a href=#browsing-context>browsing
context</a>'s <code><a href=#windowproxy>WindowProxy</a></code> object, not the actual
<code>AbstractView</code> object of the <a href=#default-view>default
- view</a>. <a href=#refsDOM3VIEWS>[DOM3VIEWS]</a></p>
+ view</a>. <a href=#refsDOMVIEWS>[DOMVIEWS]</a></p>
</div>
<p class=note>The <code title=dom-document>document</code>
attribute of an <code>AbstractView</code> object representing a
<a href=#view>view</a> gives the view's corresponding
- <code>Document</code> object. <a href=#refsDOM2VIEWS>[DOM2VIEWS]</a></p>
+ <code>Document</code> object. <a href=#refsDOMVIEWS>[DOMVIEWS]</a></p>
<p class=note>In general, there is a 1-to-1 mapping from the
<code><a href=#window>Window</a></code> object to the <code>Document</code> object. In
@@ -45956,7 +45956,7 @@
the <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#browsing-context>browsing
context</a> of that <a href=#view>view</a>, not the actual
<code>AbstractView</code> object of the <a href=#default-view>default
- view</a>. <a href=#refsDOM3EVENTS>[DOM3EVENTS]</a></p>
+ view</a>. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
</div>
@@ -48458,7 +48458,7 @@
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>
+ element. <a href=#refsDOMEVENTS>[DOMEVENTS]</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 <code title=event-click>click</code> event with no namespace, which
bubbles and is cancelable, and which uses the
@@ -51888,7 +51888,7 @@
<p>The <dfn id=dom-popstateevent-initpopstateevent title=dom-PopStateEvent-initPopStateEvent><code>initPopStateEvent()</code></dfn>
and <dfn id=dom-popstateevent-initpopstateeventns title=dom-PopStateEvent-initPopStateEventNS><code>initPopStateEventNS()</code></dfn>
methods must initialize the event in a manner analogous to the
- similarly-named methods in the DOM3 Events interfaces. <a href=#refsDOM3EVENTS>[DOM3EVENTS]</a></p>
+ similarly-named methods in the DOM Events interfaces. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
<p>The <dfn id=dom-popstateevent-state title=dom-PopStateEvent-state><code>state</code></dfn>
attribute represents the context information for the event, or null,
@@ -52604,7 +52604,7 @@
<p>When faced with displaying an XML file inline, user agents must
first <a href=#create-a-document-object>create a <code>Document</code> object</a>, following
the requirements of the XML and Namespaces in XML recommendations,
- RFC 3023, DOM3 Core, and other relevant specifications. <a href=#refsXML>[XML]</a> <a href=#refsXMLNS>[XMLNS]</a> <a href=#refsRFC3023>[RFC3023]</a> <a href=#refsDOM3CORE>[DOM3CORE]</a></p>
+ RFC 3023, DOM3 Core, and other relevant specifications. <a href=#refsXML>[XML]</a> <a href=#refsXMLNS>[XMLNS]</a> <a href=#refsRFC3023>[RFC3023]</a> <a href=#refsDOMCORE>[DOMCORE]</a></p>
<p>The actual HTTP headers and other metadata, not the headers as
mutated or implied by the algorithms given in this specification,
@@ -55197,7 +55197,7 @@
<p>The <code><a href=#selection-0>Selection</a></code> interface is represents a list of
<code>Range</code> objects. The first item in the list has index 0,
and the last item has index <var title="">count</var>-1, where
- <var title="">count</var> is the number of ranges in the list. <a href=#refsDOM2RANGE>[DOM2RANGE]</a></p>
+ <var title="">count</var> is the number of ranges in the list. <a href=#refsDOMRANGE>[DOMRANGE]</a></p>
<p>All of the members of the <code><a href=#selection-0>Selection</a></code> interface are
defined in terms of operations on the <code>Range</code> objects
@@ -56211,7 +56211,7 @@
<p>The <dfn id=dom-dragevent-initdragevent title=dom-DragEvent-initDragEvent><code>initDragEvent()</code></dfn>
and <dfn id=dom-dragevent-initdrageventns title=dom-DragEvent-initDragEventNS><code>initDragEventNS()</code></dfn>
methods must initialize the event in a manner analogous to the
- similarly-named methods in the DOM3 Events interfaces. <a href=#refsDOM3EVENTS>[DOM3EVENTS]</a></p>
+ similarly-named methods in the DOM Events interfaces. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
<p class=note>The <code title=dom-DragEvent-initDragEvent><a href=#dom-dragevent-initdragevent>initDragEvent()</a></code> and <code title=dom-DragEvent-initDragEventNS><a href=#dom-dragevent-initdrageventns>initDragEventNS()</a></code>
methods handle modifier keys differently, much like the equivalent
@@ -57565,7 +57565,7 @@
<p>The <dfn id=dom-undomanagerevent-initundomanagerevent title=dom-UndoManagerEvent-initUndoManagerEvent><code>initUndoManagerEvent()</code></dfn>
and <dfn id=initundomanagereventns()><code title=dom-UndoManagerEvent-initUndoManagerEventNS>initUndoManagerEventNS()</code></dfn>
methods must initialize the event in a manner analogous to the
- similarly-named methods in the DOM3 Events interfaces. <a href=#refsDOM3EVENTS>[DOM3EVENTS]</a></p>
+ similarly-named methods in the DOM Events interfaces. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
<p>The <dfn id=dom-undomanagerevent-data title=dom-UndoManagerEvent-data><code>data</code></dfn>
attribute represents the <a href=#undo-object>undo object</a> for the event.</p>
@@ -58129,7 +58129,7 @@
<p>The <dfn id=dom-messageevent-initmessageevent title=dom-MessageEvent-initMessageEvent><code>initMessageEvent()</code></dfn>
and <dfn id=dom-messageevent-initmessageeventns title=dom-MessageEvent-initMessageEventNS><code>initMessageEventNS()</code></dfn>
methods must initialize the event in a manner analogous to the
- similarly-named methods in the DOM3 Events interfaces. <a href=#refsDOM3EVENTS>[DOM3EVENTS]</a></p>
+ similarly-named methods in the DOM Events interfaces. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
<p>The <dfn id=dom-messageevent-data title=dom-MessageEvent-data><code>data</code></dfn>
attribute represents the message being sent.</p>
@@ -62176,7 +62176,7 @@
<p id=mutation-during-parsing>DOM mutation events must not fire
for changes caused by the UA parsing the document. (Conceptually,
the parser is not mutating the DOM, it is constructing it.) This
- includes the parsing of any content inserted using <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code> and <code title=dom-document-writeln><a href=#dom-document-writeln>document.writeln()</a></code> calls. <a href=#refsDOM3EVENTS>[DOM3EVENTS]</a></p>
+ includes the parsing of any content inserted using <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code> and <code title=dom-document-writeln><a href=#dom-document-writeln>document.writeln()</a></code> calls. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
<p class=note>Not all of the tag names mentioned below are
conformant tag names in this specification; many are included to
Modified: source
===================================================================
--- source 2009-08-08 07:58:40 UTC (rev 3566)
+++ source 2009-08-08 08:20:04 UTC (rev 3567)
@@ -704,7 +704,7 @@
node, including <code>CDATASection</code> nodes; specifically, any
<code>Node</code> with node type <code title="">TEXT_NODE</code> (3)
or <code title="">CDATA_SECTION_NODE</code> (4). <a
- href="#refsDOM3CORE">[DOM3CORE]</a></p>
+ href="#refsDOMCORE">[DOMCORE]</a></p>
<p>A content attribute is said to <dfn title="">change</dfn> value
only if its new value is different than its previous value; setting
@@ -731,7 +731,7 @@
<p>The terms <dfn title="">fire</dfn> and <dfn title="">dispatch</dfn> are used
interchangeably in the context of events, as in the DOM Events
- specifications. <a href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
+ specifications. <a href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
<h4>Plugins</h4>
@@ -1153,13 +1153,13 @@
model — of a document and its content. The DOM is not just
an API; the conformance criteria of HTML implementations are
defined, in this specification, in terms of operations on the DOM.
- <a href="#refsDOM3CORE">[DOM3CORE]</a></p>
+ <a href="#refsDOMCORE">[DOMCORE]</a></p>
<p>Implementations must support some version of DOM Core and DOM
Events, because this specification is defined in terms of the DOM,
and some of the features are defined as extensions to the DOM Core
- interfaces. <a href="#refsDOM3CORE">[DOM3CORE]</a> <a
- href="#refsDOM3CORE">[DOM3EVENTS]</a></p>
+ interfaces. <a href="#refsDOMCORE">[DOMCORE]</a> <a
+ href="#refsDOMCORE">[DOMEVENTS]</a></p>
</dd>
@@ -6345,7 +6345,7 @@
<p>DOM3 Core defines mechanisms for checking for interface support,
and for obtaining implementations of interfaces, using <a
href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMFeatures">feature
- strings</a>. <a href="#refsDOM3CORE">[DOM3CORE]</a></p>
+ strings</a>. <a href="#refsDOMCORE">[DOMCORE]</a></p>
<p>Authors are strongly discouraged from using these, as they are
notoriously unreliable and imprecise. Authors are encouraged to rely
@@ -6435,7 +6435,7 @@
<p>Every XML and HTML document in an HTML UA is represented by a
<code>Document</code> object. <a
- href="#refsDOM3CORE">[DOM3CORE]</a></p>
+ href="#refsDOMCORE">[DOMCORE]</a></p>
<p><dfn>The document's address</dfn> is an <span>absolute URL</span>
that is set when the <code>Document</code> is created. <dfn>The
@@ -6717,7 +6717,7 @@
indicated by <span>the document's address</span> over HTTP, as per
RFC 2109 section 4.3.4 or later specifications, excluding HTTP-only
cookies. <a href="#refsRFC2109">[RFC2109]</a> <a
- href="#refsRFC2965">[RFC2965]</a></p>
+ href="#refsCOOKIES">[COOKIES]</a></p>
<p>On setting, if the document is not associated with a
<span>browsing context</span> then the user agent must raise an
@@ -6735,7 +6735,7 @@
specified value, as per RFC 2109 sections 4.3.1, 4.3.2, and 4.3.3 or
later specifications, but without overwriting the values of
HTTP-only cookies. <a href="#refsRFC2109">[RFC2109]</a> <a
- href="#refsRFC2965">[RFC2965]</a></p>
+ href="#refsCOOKIES">[COOKIES]</a></p>
<p class="note">This specification does not define what makes an
HTTP-only cookie, and at the time of publication the editor is not
@@ -9156,9 +9156,9 @@
<p>For <span>HTML documents</span>, and for <span>HTML
elements</span> in <span>HTML documents</span>, certain APIs defined
- in DOM3 Core become case-insensitive or case-changing, as sometimes
- defined in DOM3 Core, and as summarized <span class="impl">or
- required</span> below. <a href="#refsDOM3CORE">[DOM3CORE]</a>.</p>
+ in DOM Core become case-insensitive or case-changing, as sometimes
+ defined in DOM Core, and as summarized <span class="impl">or
+ required</span> below. <a href="#refsDOMCORE">[DOMCORE]</a>.</p>
<p>This does not apply to <span>XML documents</span> or to elements
that are not in the <span>HTML namespace</span> despite being in
@@ -10716,7 +10716,7 @@
these headers are to be processed and resolved according to the
rules given in HTTP; the rules of <em>this</em> specification don't
apply.) <a href="#refsHTTP">[HTTP]</a> <a
- href="#refsRFC2068">[RFC2068]</a></p>
+ href="#refsWEBLINK">[WEBLINK]</a></p> <!-- WEBLINK is ref for Link: header -->
<p>The DOM attributes <dfn
title="dom-link-href"><code>href</code></dfn>, <dfn
@@ -17425,7 +17425,7 @@
Authors are encouraged to use MathML for marking up mathematics, but
authors may opt to use <code>sub</code> and <code>sup</code> if
detailed mathematical markup is not desired. <a
- href="#refsMathML">[MathML]</a></p>
+ href="#refsMATHML">[MATHML]</a></p>
<div class="example">
<pre><var>E</var>=<var>m</var><var>c</var><sup>2</sup></pre>
@@ -27848,7 +27848,7 @@
nearest integer using the IEEE 754r
<i>convertToIntegerTiesToEven</i> rounding mode. <a
href="#refsECMA262">[ECMA262]</a> <a
- href="#refsIEEE754r">[IEEE754R]</a></p>
+ href="#refsIEEE754R">[IEEE754R]</a></p>
<p class="note">The width and height (<var title="">w</var> and <var
title="">h</var>) might be different from the <var title="">sw</var>
@@ -44412,7 +44412,7 @@
title="">index</var>th row in the selection. If the argument is out
of range (less than zero or greater than the number of selected rows
minus one), then it must raise an <code>INDEX_SIZE_ERR</code>
- exception. <a href="#refsDOM3CORE">[DOM3CORE]</a></p>
+ exception. <a href="#refsDOMCORE">[DOMCORE]</a></p>
<p>The <dfn
title="dom-DataGridSelection-isSelected"><code>isSelected()</code></dfn>
@@ -51852,7 +51852,7 @@
<code>Document</code> object in some media. A view may be
interactive. Each view is represented by an
<code>AbstractView</code> object. <a
- href="#refsDOM2VIEWS">[DOM2VIEWS]</a></p>
+ href="#refsDOMVIEWS">[DOMVIEWS]</a></p>
<p>The main <span>view</span> through which a user primarily
interacts with a user agent is the <dfn>default view</dfn>. The
@@ -51870,7 +51870,7 @@
<code>DocumentView</code> interface must return the <span>browsing
context</span>'s <code>WindowProxy</code> object, not the actual
<code>AbstractView</code> object of the <span>default
- view</span>. <a href="#refsDOM3VIEWS">[DOM3VIEWS]</a></p>
+ view</span>. <a href="#refsDOMVIEWS">[DOMVIEWS]</a></p>
</div>
@@ -51878,7 +51878,7 @@
attribute of an <code>AbstractView</code> object representing a
<span>view</span> gives the view's corresponding
<code>Document</code> object. <a
- href="#refsDOM2VIEWS">[DOM2VIEWS]</a></p>
+ href="#refsDOMVIEWS">[DOMVIEWS]</a></p>
<p class="note">In general, there is a 1-to-1 mapping from the
<code>Window</code> object to the <code>Document</code> object. In
@@ -51899,7 +51899,7 @@
the <code>WindowProxy</code> object of the <span>browsing
context</span> of that <span>view</span>, not the actual
<code>AbstractView</code> object of the <span>default
- view</span>. <a href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
+ view</span>. <a href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
</div>
@@ -54777,7 +54777,7 @@
elements. For example, the <code title="dom-click">click()</code>
method on the <code>HTMLElement</code> interface is defined as
firing a <code title="event-click">click</code> event on the
- element. <a href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
+ element. <a href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
<p><dfn title="fire a click event">Firing a <code
title="event-click">click</code> event</dfn> means that a <code
@@ -58765,8 +58765,8 @@
and <dfn
title="dom-PopStateEvent-initPopStateEventNS"><code>initPopStateEventNS()</code></dfn>
methods must initialize the event in a manner analogous to the
- similarly-named methods in the DOM3 Events interfaces. <a
- href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
+ similarly-named methods in the DOM Events interfaces. <a
+ href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
<p>The <dfn title="dom-PopStateEvent-state"><code>state</code></dfn>
attribute represents the context information for the event, or null,
@@ -59600,7 +59600,7 @@
RFC 3023, DOM3 Core, and other relevant specifications. <a
href="#refsXML">[XML]</a> <a href="#refsXMLNS">[XMLNS]</a> <a
href="#refsRFC3023">[RFC3023]</a> <a
- href="#refsDOM3CORE">[DOM3CORE]</a></p>
+ href="#refsDOMCORE">[DOMCORE]</a></p>
<p>The actual HTTP headers and other metadata, not the headers as
mutated or implied by the algorithms given in this specification,
@@ -60582,8 +60582,8 @@
and <dfn
title="dom-StorageEvent-initStorageEventNS"><code>initStorageEventNS()</code></dfn>
methods must initialize the event in a manner analogous to the
- similarly-named methods in the DOM3 Events interfaces. <a
- href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
+ similarly-named methods in the DOM Events interfaces. <a
+ href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
<p>The <dfn title="dom-StorageEvent-key"><code>key</code></dfn>
attribute represents the key being changed.</p>
@@ -64290,7 +64290,7 @@
<code>Range</code> objects. The first item in the list has index 0,
and the last item has index <var title="">count</var>-1, where
<var title="">count</var> is the number of ranges in the list. <a
- href="#refsDOM2RANGE">[DOM2RANGE]</a></p>
+ href="#refsDOMRANGE">[DOMRANGE]</a></p>
<p>All of the members of the <code>Selection</code> interface are
defined in terms of operations on the <code>Range</code> objects
@@ -65461,8 +65461,8 @@
and <dfn
title="dom-DragEvent-initDragEventNS"><code>initDragEventNS()</code></dfn>
methods must initialize the event in a manner analogous to the
- similarly-named methods in the DOM3 Events interfaces. <a
- href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
+ similarly-named methods in the DOM Events interfaces. <a
+ href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
<p class="note">The <code
title="dom-DragEvent-initDragEvent">initDragEvent()</code> and <code
@@ -67109,8 +67109,8 @@
and <dfn><code
title="dom-UndoManagerEvent-initUndoManagerEventNS">initUndoManagerEventNS()</code></dfn>
methods must initialize the event in a manner analogous to the
- similarly-named methods in the DOM3 Events interfaces. <a
- href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
+ similarly-named methods in the DOM Events interfaces. <a
+ href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
<p>The <dfn title="dom-UndoManagerEvent-data"><code>data</code></dfn>
attribute represents the <span>undo object</span> for the event.</p>
@@ -68698,8 +68698,8 @@
and <dfn
title="dom-ErrorEvent-initErrorEventNS"><code>initErrorEventNS()</code></dfn>
methods must initialize the event in a manner analogous to the
- similarly-named methods in the DOM3 Events interfaces. <a
- href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
+ similarly-named methods in the DOM Events interfaces. <a
+ href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
<p>The <dfn title="dom-ErrorEvent-message"><code>message</code></dfn>
attribute represents the error message.</p>
@@ -69430,8 +69430,8 @@
and <dfn
title="dom-MessageEvent-initMessageEventNS"><code>initMessageEventNS()</code></dfn>
methods must initialize the event in a manner analogous to the
- similarly-named methods in the DOM3 Events interfaces. <a
- href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
+ similarly-named methods in the DOM Events interfaces. <a
+ href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
<p>The <dfn
title="dom-MessageEvent-data"><code>data</code></dfn>
@@ -69514,7 +69514,7 @@
<p><code>EventSource</code> objects must also implement the
<code>EventTarget</code> interface. <a
- href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
+ href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
<p>The <dfn title="dom-EventSource"><code>EventSource(<var
title="">url</var>)</code></dfn> constructor takes one argument,
@@ -70268,7 +70268,7 @@
<p><code>WebSocket</code> objects must also implement the
<code>EventTarget</code> interface. <a
- href="#refsDOM3EVENTS">[DOM3EVENTS]</a>
+ href="#refsDOMEVENTS">[DOMEVENTS]</a>
<p>The <dfn title="dom-WebSocket"><code>WebSocket(<var
title="">url</var>, <var title="">protocol</var>)</code></dfn>
@@ -76452,7 +76452,7 @@
includes the parsing of any content inserted using <code
title="dom-document-write">document.write()</code> and <code
title="dom-document-writeln">document.writeln()</code> calls. <a
- href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
+ href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
<p class="note">Not all of the tag names mentioned below are
conformant tag names in this specification; many are included to
More information about the Commit-Watchers
mailing list