[html5] r7506 - [] (0) Try to be more normatively tight about 'fire' and 'dispatch'. Fixing http [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Nov 5 13:38:05 PST 2012
Author: ianh
Date: 2012-11-05 13:38:04 -0800 (Mon, 05 Nov 2012)
New Revision: 7506
Modified:
complete.html
index
source
Log:
[] (0) Try to be more normatively tight about 'fire' and 'dispatch'.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=16063
Affected topics: DOM APIs, HTML, HTML Syntax and Parsing, Offline Web Applications, Server-Sent Events, Video Text Tracks, Video and Audio, Web Storage, Web Workers, WebSocket API
Modified: complete.html
===================================================================
--- complete.html 2012-11-05 21:05:36 UTC (rev 7505)
+++ complete.html 2012-11-05 21:38:04 UTC (rev 7506)
@@ -3468,13 +3468,12 @@
operate on the actual underlying data, not a snapshot of the
data.</p>
- <p>In the contexts of events, the terms <dfn title="">fire</dfn> and
- <dfn id=concept-event-dispatch title=concept-event-dispatch>dispatch</dfn> are used as
- defined in the DOM Core specification: firing an event means to
- create and dispatch it, and dispatching an event means to follow the
- steps that propagate the event through the tree. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is used to refer
- to events whose <code title=dom-event-isTrusted><a href=#dom-event-istrusted>isTrusted</a></code>
- attribute is initialized to true. <a href=#refsDOMCORE>[DOMCORE]</a></p>
+ <p>In the contexts of events, the terms <i>fire</i> and <i>dispatch</i> are used as defined in the
+ DOM Core specification: <dfn id=concept-event-fire title=concept-event-fire>firing</dfn> an event means to create and
+ <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> it, and <dfn id=concept-event-dispatch title=concept-event-dispatch>dispatching</dfn> an event means to follow the steps that propagate
+ the event through the tree. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is
+ used to refer to events whose <code title=dom-event-isTrusted><a href=#dom-event-istrusted>isTrusted</a></code> attribute is
+ initialized to true. <a href=#refsDOMCORE>[DOMCORE]</a></p>
<h4 id=plugins><span class=secno>2.1.5 </span>Plugins</h4>
@@ -12816,8 +12815,7 @@
<li>
- <p>Dispatch the required <code title=event-click><a href=#event-click>click</a></code>
- event.</p> <!-- interaction event spec point -->
+ <p><a href=#concept-event-dispatch title=concept-event-dispatch>Dispatch</a> the required <code title=event-click><a href=#event-click>click</a></code> event.</p> <!-- interaction event spec point -->
<p>If there is an element <var title="">e</var> and the <code title=event-click><a href=#event-click>click</a></code> event is not canceled, <a href=#run-post-click-activation-steps>run
post-click activation steps</a> on element <var title="">e</var>.</p>
@@ -30108,11 +30106,9 @@
<code><a href=#audiotracklist>AudioTrackList</a></code> object with the new
<code><a href=#audiotrack>AudioTrack</a></code> object.</li>
- <li><p>Fire an event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and
- is not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized
- to the new <code><a href=#audiotrack>AudioTrack</a></code> object, at this
- <code><a href=#audiotracklist>AudioTrackList</a></code> object.</li>
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to the new
+ <code><a href=#audiotrack>AudioTrack</a></code> object, at this <code><a href=#audiotracklist>AudioTrackList</a></code> object.</li>
</ol></dd>
@@ -30129,11 +30125,9 @@
<code><a href=#videotracklist>VideoTrackList</a></code> object with the new
<code><a href=#videotrack>VideoTrack</a></code> object.</li>
- <li><p>Fire an event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and
- is not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized
- to the new <code><a href=#videotrack>VideoTrack</a></code> object, at this
- <code><a href=#videotracklist>VideoTrackList</a></code> object.</li>
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to the new
+ <code><a href=#videotrack>VideoTrack</a></code> object, at this <code><a href=#videotracklist>VideoTrackList</a></code> object.</li>
</ol></dd>
@@ -30819,23 +30813,17 @@
<!-- see https://www.w3.org/Bugs/Public/show_bug.cgi?id=14492 -->
<!-- basically this is to handle very-long-running streams that use
different video and audio tracks per TV show -->
- <p>If at any time the user agent learns that an audio or video track
- has ended and all <a href=#media-data>media data</a> relating to that track
- corresponds to parts of the <a href=#media-timeline>media timeline</a> that are
- <em>before</em> the <a href=#earliest-possible-position>earliest possible position</a>, the
- user agent may <a href=#queue-a-task>queue a task</a> to remove the track from
- the <code title=dom-media-audioTracks><a href=#dom-media-audiotracks>audioTracks</a></code>
- attribute's <code><a href=#audiotracklist>AudioTrackList</a></code> object or the <code title=dom-media-videoTracks><a href=#dom-media-videotracks>videoTracks</a></code> attribute's
- <code><a href=#videotracklist>VideoTrackList</a></code> object as appropriate and then fire an
- event with the name <code title=event-removetrack>removetrack</code>, that does not bubble
- and is not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code>
- attribute initialized to the <code><a href=#audiotrack>AudioTrack</a></code> or
- <code><a href=#videotrack>VideoTrack</a></code> object representing the track, at the
- <a href=#media-element>media element</a>'s aforementioned
- <code><a href=#audiotracklist>AudioTrackList</a></code> or <code><a href=#videotracklist>VideoTrackList</a></code>
- object.</p>
+ <p>If at any time the user agent learns that an audio or video track has ended and all <a href=#media-data>media
+ data</a> relating to that track corresponds to parts of the <a href=#media-timeline>media timeline</a> that
+ are <em>before</em> the <a href=#earliest-possible-position>earliest possible position</a>, the user agent may <a href=#queue-a-task>queue a
+ task</a> to remove the track from the <code title=dom-media-audioTracks><a href=#dom-media-audiotracks>audioTracks</a></code>
+ attribute's <code><a href=#audiotracklist>AudioTrackList</a></code> object or the <code title=dom-media-videoTracks><a href=#dom-media-videotracks>videoTracks</a></code> attribute's <code><a href=#videotracklist>VideoTrackList</a></code> object as
+ appropriate and then <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-removetrack>removetrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to the <code><a href=#audiotrack>AudioTrack</a></code> or
+ <code><a href=#videotrack>VideoTrack</a></code> object representing the track, at the <a href=#media-element>media element</a>'s
+ aforementioned <code><a href=#audiotracklist>AudioTrackList</a></code> or <code><a href=#videotracklist>VideoTrackList</a></code> object.</p>
+
<p>The <dfn id=dom-media-duration title=dom-media-duration><code>duration</code></dfn>
attribute must return the time of the end of the <a href=#media-resource>media
resource</a>, in seconds, on the <a href=#media-timeline>media timeline</a>. If
@@ -34160,12 +34148,10 @@
<li><p>Add the new <a href=#text-track>text track</a> to the <a href=#media-element>media
element</a>'s <a href=#list-of-text-tracks>list of text tracks</a>.</li>
- <li><p>Fire an event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is
- not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code>
- attribute initialized to the <a href=#text-track>text track</a>'s
- <code><a href=#texttrack>TextTrack</a></code> object, at the <a href=#media-element>media element</a>'s
- <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is not cancelable, and that uses
+ the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code>
+ attribute initialized to the <a href=#text-track>text track</a>'s <code><a href=#texttrack>TextTrack</a></code> object, at the
+ <a href=#media-element>media element</a>'s <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's
<code><a href=#texttracklist>TextTrackList</a></code> object.</li>
</ol><!-- removetrack: we don't currently ever remove an in-band text
@@ -34238,30 +34224,22 @@
<a href=#webvtt>WebVTT</a>, this is the <a href=#rules-for-updating-the-display-of-webvtt-text-tracks>rules for updating the
display of WebVTT text tracks</a>. <a href=#refsWEBVTT>[WEBVTT]</a></p>
- <p>When a <code><a href=#the-track-element>track</a></code> element's parent element changes and
- the new parent is a <a href=#media-element>media element</a>, then the user agent
- must add the <code><a href=#the-track-element>track</a></code> element's corresponding <a href=#text-track>text
- track</a> to the <a href=#media-element>media element</a>'s <a href=#list-of-text-tracks>list of text
- tracks</a>, and then <a href=#queue-a-task>queue a task</a> to fire an event
- with the name <code title=event-addtrack>addtrack</code>, that
- does not bubble and is not cancelable, and that uses the
- <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to
- the <a href=#text-track>text track</a>'s <code><a href=#texttrack>TextTrack</a></code> object, at the
+ <p>When a <code><a href=#the-track-element>track</a></code> element's parent element changes and the new parent is a <a href=#media-element>media
+ element</a>, then the user agent must add the <code><a href=#the-track-element>track</a></code> element's corresponding
+ <a href=#text-track>text track</a> to the <a href=#media-element>media element</a>'s <a href=#list-of-text-tracks>list of text tracks</a>, and
+ then <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is not cancelable, and that uses
+ the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code>
+ attribute initialized to the <a href=#text-track>text track</a>'s <code><a href=#texttrack>TextTrack</a></code> object, at the
<a href=#media-element>media element</a>'s <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's
<code><a href=#texttracklist>TextTrackList</a></code> object.</p>
- <p>When a <code><a href=#the-track-element>track</a></code> element's parent element changes and
- the old parent was a <a href=#media-element>media element</a>, then the user agent
- must remove the <code><a href=#the-track-element>track</a></code> element's corresponding
- <a href=#text-track>text track</a> from the <a href=#media-element>media element</a>'s
- <a href=#list-of-text-tracks>list of text tracks</a>, and then <a href=#queue-a-task>queue a task</a>
- to fire an event with the name <code title=event-removetrack>removetrack</code>, that does not bubble
- and is not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code>
- attribute initialized to the <a href=#text-track>text track</a>'s
- <code><a href=#texttrack>TextTrack</a></code> object, at the <a href=#media-element>media element</a>'s
- <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's
- <code><a href=#texttracklist>TextTrackList</a></code> object.</p> <!-- removetrack -->
+ <p>When a <code><a href=#the-track-element>track</a></code> element's parent element changes and the old parent was a <a href=#media-element>media
+ element</a>, then the user agent must remove the <code><a href=#the-track-element>track</a></code> element's corresponding
+ <a href=#text-track>text track</a> from the <a href=#media-element>media element</a>'s <a href=#list-of-text-tracks>list of text tracks</a>,
+ and then <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-removetrack>removetrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to the <a href=#text-track>text track</a>'s
+ <code><a href=#texttrack>TextTrack</a></code> object, at the <a href=#media-element>media element</a>'s <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's <code><a href=#texttracklist>TextTrackList</a></code> object.</p>
+ <!-- removetrack -->
<hr><p>When a <a href=#text-track>text track</a> corresponding to a
<code><a href=#the-track-element>track</a></code> element is added to a <a href=#media-element>media
@@ -34821,12 +34799,10 @@
<li>
- <p><a href=#queue-a-task>Queue a task</a> to fire an event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and
- is not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to
- the new <a href=#text-track>text track</a>'s <code><a href=#texttrack>TextTrack</a></code> object,
- at the <a href=#media-element>media element</a>'s <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's
- <code><a href=#texttracklist>TextTrackList</a></code> object.</p>
+ <p><a href=#queue-a-task>Queue a task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to the new <a href=#text-track>text
+ track</a>'s <code><a href=#texttrack>TextTrack</a></code> object, at the <a href=#media-element>media element</a>'s <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's <code><a href=#texttracklist>TextTrackList</a></code>
+ object.</p>
</li>
@@ -59164,13 +59140,11 @@
<dl class=switch><dt>If the user requested a context menu using a pointing device</dt>
- <dd><p>The user agent must fire an event with the name <code title=event-contextmenu>contextmenu</code>, that bubbles and is
- cancelable, and that uses the <code><a href=#mouseevent>MouseEvent</a></code> interface, at
- the element for which the menu was requested. The context
- information of the event must be initialized to the same values as
- the last <code><a href=#mouseevent>MouseEvent</a></code> user interaction event that was
- fired as part of the gesture that that was interpreted as a request
- for the context menu.</dd>
+ <dd><p>The user agent must <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-contextmenu>contextmenu</code>, that bubbles and is cancelable, and that uses the
+ <code><a href=#mouseevent>MouseEvent</a></code> interface, at the element for which the menu was requested. The context
+ information of the event must be initialized to the same values as the last
+ <code><a href=#mouseevent>MouseEvent</a></code> user interaction event that was fired as part of the gesture that that
+ was interpreted as a request for the context menu.</dd>
<dt>Otherwise</dt>
@@ -71435,14 +71409,11 @@
<li><p>Set the <code><a href=#document>Document</a></code>'s <a href=#page-showing>page
showing</a> flag to true.</li>
- <li><p>Fire a <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code>
- event at the <code><a href=#window>Window</a></code> object of that
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code> at the <code><a href=#window>Window</a></code> object of that
<code><a href=#document>Document</a></code>, but with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to the
- <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the
- <code><a href=#window>Window</a></code> object), using the
- <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface, with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code>
- attribute initialized to true. This event must not bubble, must
- not be cancelable, and has no default action.</li>
+ <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the <code><a href=#window>Window</a></code> object),
+ using the <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface, with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code> attribute initialized to true.
+ This event must not bubble, must not be cancelable, and has no default action.</li>
</ol><!-- an interesting thing to test would be to traverse back
during onload, before the first pageshow has fired, and then to
@@ -71504,19 +71475,17 @@
<code><a href=#document>Document</a></code> of the <var title="">specified entry</var> be
the <var title="">specified entry</var>.</li>
- <li><p>If <var title="">state changed</var> is true, fire a <code title=event-popstate><a href=#event-popstate>popstate</a></code> event at the
- <code><a href=#window>Window</a></code> object of the <code><a href=#document>Document</a></code>, using the
- <code><a href=#popstateevent>PopStateEvent</a></code> interface, with the <code title=dom-PopStateEvent-state><a href=#dom-popstateevent-state>state</a></code> attribute initialized
- to the value of <var title="">state</var>. This event must bubble
- but not be cancelable and has no default action.</li>
+ <li><p>If <var title="">state changed</var> is true, <a href=#concept-event-fire title=concept-event-fire>fire</a>
+ a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-popstate><a href=#event-popstate>popstate</a></code> at the <code><a href=#window>Window</a></code> object of the
+ <code><a href=#document>Document</a></code>, using the <code><a href=#popstateevent>PopStateEvent</a></code> interface, with the <code title=dom-PopStateEvent-state><a href=#dom-popstateevent-state>state</a></code> attribute initialized to the value of <var title="">state</var>. This event must bubble but not be cancelable and has no default
+ action.</li>
- <li><p>If <var title="">hash changed</var> is true, then fire a
- <code title=event-hashchange><a href=#event-hashchange>hashchange</a></code> event at the
- <a href=#browsing-context>browsing context</a>'s <code><a href=#window>Window</a></code> object, using
- the <code><a href=#hashchangeevent>HashChangeEvent</a></code> interface, with the <code title=dom-HashChangeEvent-oldURL><a href=#dom-hashchangeevent-oldurl>oldURL</a></code> attribute
- initialized to <var title="">old URL</var> and the <code title=dom-HashChangeEvent-newURL><a href=#dom-hashchangeevent-newurl>newURL</a></code> attribute
- initialized to <var title="">new URL</var>. This event must bubble
- but not be cancelable and has no default action.</li>
+ <li><p>If <var title="">hash changed</var> is true, then <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>
+ event with the name <code title=event-hashchange><a href=#event-hashchange>hashchange</a></code> at the <a href=#browsing-context>browsing
+ context</a>'s <code><a href=#window>Window</a></code> object, using the <code><a href=#hashchangeevent>HashChangeEvent</a></code> interface,
+ with the <code title=dom-HashChangeEvent-oldURL><a href=#dom-hashchangeevent-oldurl>oldURL</a></code> attribute initialized to <var title="">old URL</var> and the <code title=dom-HashChangeEvent-newURL><a href=#dom-hashchangeevent-newurl>newURL</a></code> attribute
+ initialized to <var title="">new URL</var>. This event must bubble but not be cancelable and has
+ no default action.</li>
<li><p>The <a href=#current-entry>current entry</a> is now the <var title="">specified entry</var>.</li>
@@ -71674,8 +71643,7 @@
<li><p>Let <var title="">event</var> be a new <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>
<code><a href=#beforeunloadevent>BeforeUnloadEvent</a></code> event object with the name <code title=event-beforeunload>beforeunload</code>, which does not bubble but is cancelable.</li>
- <li><p><i>Dispatch</i>: Dispatch <var title="">event</var> at the
- <code><a href=#document>Document</a></code>'s <code><a href=#window>Window</a></code> object.</li>
+ <li><p><i>Dispatch</i>: <a href=#concept-event-dispatch title=concept-event-dispatch>Dispatch</a> <var title="">event</var> at the <code><a href=#document>Document</a></code>'s <code><a href=#window>Window</a></code> object.</li>
<li><p>Decrease the <a href=#event-loop>event loop</a>'s <a href=#termination-nesting-level>termination
nesting level</a> by one.</li>
@@ -71759,14 +71727,12 @@
<li><p>Set the <code><a href=#document>Document</a></code>'s <a href=#page-showing>page showing</a>
flag to false.</li>
- <li><p>Fire a <code title=event-pagehide><a href=#event-pagehide>pagehide</a></code> event at
- the <code><a href=#window>Window</a></code> object of the <code><a href=#document>Document</a></code>, but
- with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to the
- <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the
- <code><a href=#window>Window</a></code> object), using the
- <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface, with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code>
- attribute initialized to true. This event must not bubble, must not
- be cancelable, and has no default action.</li>
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-pagehide><a href=#event-pagehide>pagehide</a></code> at the <code><a href=#window>Window</a></code> object of the
+ <code><a href=#document>Document</a></code>, but with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to the
+ <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code>
+ set to the <code><a href=#window>Window</a></code> object), using the <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface,
+ with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code> attribute initialized
+ to true. This event must not bubble, must not be cancelable, and has no default action.</li>
<li>
@@ -73348,23 +73314,17 @@
</li>
- <li><p>For each <a href=#cache-host>cache host</a> associated with an
- <a href=#application-cache>application cache</a> in <var title="">cache
- group</var>, <a href=#queue-a-post-load-task>queue a post-load task</a> to fire an event
- with the name <code title=event-appcache-progress><a href=#event-appcache-progress>progress</a></code>, which does not
- bubble, which is cancelable, and which uses the
- <code>ProgressEvent</code> interface, at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
- host</a>. The <code title=dom-ProgressEvents-lengthComputable>lengthComputable</code>
- attribute must be set to true, the <code title=dom-ProgressEvents-total>total</code> attribute must be
- set to the number of files in <var title="">file list</var>, and
- the <code title=dom-ProgressEvents-loaded>loaded</code>
- attribute must be set to the number of files in <var title="">file list</var> that have been either downloaded or
- skipped so far. The default action of these events must be, if
- the user agent <a href=#shows-caching-progress>shows caching progress</a>, the display
- of some sort of user interface indicating to the user that a file
- is being downloaded in preparation for updating the application.
- <a href=#refsPROGRESS>[PROGRESS]</a></li>
+ <li><p>For each <a href=#cache-host>cache host</a> associated with an <a href=#application-cache>application cache</a> in
+ <var title="">cache group</var>, <a href=#queue-a-post-load-task>queue a post-load task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>
+ event with the name <code title=event-appcache-progress><a href=#event-appcache-progress>progress</a></code>, which does not
+ bubble, which is cancelable, and which uses the <code>ProgressEvent</code> interface, at the
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache host</a>. The <code title=dom-ProgressEvents-lengthComputable>lengthComputable</code> attribute must be set to
+ true, the <code title=dom-ProgressEvents-total>total</code> attribute must be set to the
+ number of files in <var title="">file list</var>, and the <code title=dom-ProgressEvents-loaded>loaded</code> attribute must be set to the number of files in
+ <var title="">file list</var> that have been either downloaded or skipped so far. The default
+ action of these events must be, if the user agent <a href=#shows-caching-progress>shows caching progress</a>, the
+ display of some sort of user interface indicating to the user that a file is being downloaded
+ in preparation for updating the application. <a href=#refsPROGRESS>[PROGRESS]</a></li>
<li>
@@ -73499,20 +73459,14 @@
</ol></li>
- <li><p>For each <a href=#cache-host>cache host</a> associated with an
- <a href=#application-cache>application cache</a> in <var title="">cache group</var>,
- <a href=#queue-a-post-load-task>queue a post-load task</a> to fire an event with the name
- <code title=event-appcache-progress><a href=#event-appcache-progress>progress</a></code>, which does
- not bubble, which is cancelable, and which uses the
- <code>ProgressEvent</code> interface, at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
- host</a>. The <code title=dom-ProgressEvents-lengthComputable>lengthComputable</code>
- attribute must be set to true, the <code title=dom-ProgressEvents-total>total</code> and the <code title=dom-ProgressEvents-loaded>loaded</code> attributes must be
- set to the number of files in <var title="">file list</var>. The
- default action of these events must be, if the user agent
- <a href=#shows-caching-progress>shows caching progress</a>, the display of some sort of
- user interface indicating to the user that all the files have been
- downloaded. <a href=#refsPROGRESS>[PROGRESS]</a></li>
+ <li><p>For each <a href=#cache-host>cache host</a> associated with an <a href=#application-cache>application cache</a> in <var title="">cache group</var>, <a href=#queue-a-post-load-task>queue a post-load task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>
+ event with the name <code title=event-appcache-progress><a href=#event-appcache-progress>progress</a></code>, which does not bubble,
+ which is cancelable, and which uses the <code>ProgressEvent</code> interface, at the
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache host</a>. The <code title=dom-ProgressEvents-lengthComputable>lengthComputable</code> attribute must be set to
+ true, the <code title=dom-ProgressEvents-total>total</code> and the <code title=dom-ProgressEvents-loaded>loaded</code> attributes must be set to the number of files in
+ <var title="">file list</var>. The default action of these events must be, if the user agent
+ <a href=#shows-caching-progress>shows caching progress</a>, the display of some sort of user interface indicating to the
+ user that all the files have been downloaded. <a href=#refsPROGRESS>[PROGRESS]</a></li>
<li><p>Store the list of <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback namespaces</a>,
and the URLs of the <a href=#concept-appcache-fallback title=concept-appcache-fallback>fallback entries</a> that they
@@ -74972,11 +74926,10 @@
of related similar-origin browsing contexts</a> to which the
<a href="#script's-browsing-context">script's browsing context</a> belongs.</p>
- <p class=note>This will typically fire scripted callbacks, which
- calls the <a href=#jump-to-a-code-entry-point>jump to a code entry-point</a> algorithm, which
- calls this <a href=#perform-a-microtask-checkpoint>perform a microtask checkpoint</a> algorithm
- again, which is why we use the <a href=#running-mutation-observers>running mutation
- observers</a> flag to avoid reentrancy.</p>
+ <p class=note>This will typically invoke scripted callbacks, which calls the <a href=#jump-to-a-code-entry-point>jump to a
+ code entry-point</a> algorithm, which calls this <a href=#perform-a-microtask-checkpoint>perform a microtask checkpoint</a>
+ algorithm again, which is why we use the <a href=#running-mutation-observers>running mutation observers</a> flag to avoid
+ reentrancy.</p>
</li>
@@ -80314,8 +80267,8 @@
</li>
- <li><p>Dispatch the newly created <code><a href=#dragevent>DragEvent</a></code> object at
- the specified target element.</li>
+ <li><p><a href=#concept-event-dispatch title=concept-event-dispatch>Dispatch</a> the newly created
+ <code><a href=#dragevent>DragEvent</a></code> object at the specified target element.</li>
<li><p>Set the <a href=#drag-data-store-allowed-effects-state>drag data store allowed effects state</a>
to the current value of <var title="">dataTransfer</var>'s <code title=dom-DataTransfer-effectAllowed><a href=#dom-datatransfer-effectallowed>effectAllowed</a></code>
@@ -80799,12 +80752,10 @@
<dd><p>Reset the <a href=#current-drag-operation>current drag operation</a> to "<code title="">none</code>".</dd>
- </dl><p>Otherwise (if the <code title=event-dragover><a href=#event-dragover>dragover</a></code> event <em>is</em>
- canceled), set the <a href=#current-drag-operation>current drag operation</a> based on
- the values of the <code title=dom-DataTransfer-effectAllowed><a href=#dom-datatransfer-effectallowed>effectAllowed</a></code> and
- <code title=dom-DataTransfer-dropEffect><a href=#dom-datatransfer-dropeffect>dropEffect</a></code>
- attributes of the <code><a href=#dragevent>DragEvent</a></code> object's <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code> object as
- they stood after the event dispatch finished, as per the
+ </dl><p>Otherwise (if the <code title=event-dragover><a href=#event-dragover>dragover</a></code> event <em>is</em> canceled),
+ set the <a href=#current-drag-operation>current drag operation</a> based on the values of the <code title=dom-DataTransfer-effectAllowed><a href=#dom-datatransfer-effectallowed>effectAllowed</a></code> and <code title=dom-DataTransfer-dropEffect><a href=#dom-datatransfer-dropeffect>dropEffect</a></code> attributes of the <code><a href=#dragevent>DragEvent</a></code>
+ object's <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code> object as they stood
+ after the event <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> finished, as per the
following table:</p>
<table><thead><tr><th><code title=dom-DataTransfer-effectAllowed><a href=#dom-datatransfer-effectallowed>effectAllowed</a></code></th>
@@ -80886,10 +80837,11 @@
<li>
- <p>If the event is canceled, set the <a href=#current-drag-operation>current drag
- operation</a> to the value of the <code title=dom-DataTransfer-dropEffect><a href=#dom-datatransfer-dropeffect>dropEffect</a></code> attribute
- of the <code><a href=#dragevent>DragEvent</a></code> object's <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code> object
- as it stood after the event dispatch finished.</p>
+ <p>If the event is canceled, set the <a href=#current-drag-operation>current drag operation</a> to the value of the
+ <code title=dom-DataTransfer-dropEffect><a href=#dom-datatransfer-dropeffect>dropEffect</a></code> attribute of the
+ <code><a href=#dragevent>DragEvent</a></code> object's <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code>
+ object as it stood after the event <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a>
+ finished.</p>
<p>Otherwise, the event is not canceled; perform the event's
default action, which depends on the exact target as
@@ -83145,16 +83097,15 @@
may be reported to the user.
</p>
- <p>For dedicated workers, if the error is still <i title=concept-error-nothandled><a href=#concept-error-nothandled>not handled</a></i> afterwards, or if
- the error occurred while handling a previous script error, the user
- agent must <a href=#queue-a-task>queue a task</a> to fire an event that uses the
- <code><a href=#errorevent>ErrorEvent</a></code> interface, with the name <code title=event-error>error</code>, that doesn't bubble and is
- cancelable, with its <code title=dom-ErrorEvent-message><a href=#dom-errorevent-message>message</a></code>, <code title=dom-ErrorEvent-filename><a href=#dom-errorevent-filename>filename</a></code>, <code title=dom-ErrorEvent-lineno><a href=#dom-errorevent-lineno>lineno</a></code>, and <code title=dom-ErrorEvent-column><a href=#dom-errorevent-column>column</a></code> attributes initialized
- appropriately, at the <code><a href=#worker>Worker</a></code> object associated with the
- worker. If the event is not canceled, the user agent must act as if
- the uncaught runtime script error had occurred in the global scope
- that the <code><a href=#worker>Worker</a></code> object is in, thus repeating the entire
- runtime script error reporting process one level up.</p>
+ <p>For dedicated workers, if the error is still <i title=concept-error-nothandled><a href=#concept-error-nothandled>not
+ handled</a></i> afterwards, or if the error occurred while handling a previous script error, the user
+ agent must <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event that uses the <code><a href=#errorevent>ErrorEvent</a></code>
+ interface, with the name <code title=event-error>error</code>, that doesn't bubble and is
+ cancelable, with its <code title=dom-ErrorEvent-message><a href=#dom-errorevent-message>message</a></code>, <code title=dom-ErrorEvent-filename><a href=#dom-errorevent-filename>filename</a></code>, <code title=dom-ErrorEvent-lineno><a href=#dom-errorevent-lineno>lineno</a></code>, and <code title=dom-ErrorEvent-column><a href=#dom-errorevent-column>column</a></code>
+ attributes initialized appropriately, at the <code><a href=#worker>Worker</a></code> object associated with the
+ worker. If the event is not canceled, the user agent must act as if the uncaught runtime script
+ error had occurred in the global scope that the <code><a href=#worker>Worker</a></code> object is in, thus repeating
+ the entire runtime script error reporting process one level up.</p>
<p>If the implicit port connecting the worker to its
<code><a href=#worker>Worker</a></code> object has been disentangled (i.e. if the parent
@@ -83529,7 +83480,8 @@
is initialized to the empty string, has a <code title=dom-MessageEvent-ports><a href=#dom-messageevent-ports>ports</a></code>
attribute whose value is initialized to a <a href=#dfn-read-only-array title=dfn-read-only-array>read only</a>
array containing only the newly created port, and has a <code title=dom-MessageEvent-source><a href=#dom-messageevent-source>source</a></code> attribute whose value is initialized to the
- newly created port, and <a href=#queue-a-task>queue a task</a> to dispatch the event at <var title="">worker global scope</var>.</li>
+ newly created port, and <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> the event at <var title="">worker global
+ scope</var>.</li>
<li>
@@ -83584,8 +83536,8 @@
string, has a <code title=dom-MessageEvent-ports><a href=#dom-messageevent-ports>ports</a></code> attribute whose value is
initialized to a <a href=#dfn-read-only-array title=dfn-read-only-array>read only</a> array containing only the
newly created port, and has a <code title=dom-MessageEvent-source><a href=#dom-messageevent-source>source</a></code> attribute whose
- value is initialized to the newly created port, and <a href=#queue-a-task>queue a task</a> to dispatch the
- event at <var title="">worker global scope</var>.</li>
+ value is initialized to the newly created port, and <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> the event at <var title="">worker global
+ scope</var>.</li>
<li>
@@ -84520,12 +84472,10 @@
<li><p>Set the <var title="">data</var> buffer and the <var title="">event type</var> buffer to the empty string.</li>
- <li><p><a href=#queue-a-task>Queue a task</a> which, if the <code title=dom-EventSource-readyState><a href=#dom-eventsource-readystate>readyState</a></code> attribute is
- set to a value other than <code title=dom-EventSource-CLOSED><a href=#dom-eventsource-closed>CLOSED</a></code>, dispatches the newly
- created event at the <code><a href=#eventsource>EventSource</a></code> object.</li> <!--
- so calling close() drops the messages immediately. The connection
- dying doesn't interfere with already-sent messages since it sets us
- to CLOSED via a task, not synchronously -->
+ <li><p><a href=#queue-a-task>Queue a task</a> which, if the <code title=dom-EventSource-readyState><a href=#dom-eventsource-readystate>readyState</a></code> attribute is set to a value other than <code title=dom-EventSource-CLOSED><a href=#dom-eventsource-closed>CLOSED</a></code>, <a href=#concept-event-dispatch title=concept-event-dispatch>dispatches</a> the newly created event at the
+ <code><a href=#eventsource>EventSource</a></code> object.</li> <!-- so calling close() drops the messages immediately.
+ The connection dying doesn't interfere with already-sent messages since it sets us to CLOSED via
+ a task, not synchronously -->
</ol><p class=note>If an event doesn't have an "id" field, but an
earlier event did set the event source's <a href=#concept-event-stream-last-event-id title=concept-event-stream-last-event-id>last event ID
@@ -85417,7 +85367,7 @@
<li>
- <p>Dispatch <var title="">event</var> at the
+ <p><a href=#concept-event-dispatch title=concept-event-dispatch>Dispatch</a> <var title="">event</var> at the
<code><a href=#websocket>WebSocket</a></code> object.</p>
</li>
@@ -85478,7 +85428,8 @@
true if the connection closed <i title="">cleanly</i> and false otherwise, whose <code title=dom-CloseEvent-code><a href=#dom-closeevent-code>code</a></code> attribute is initialized to <i><a href=#the-websocket-connection-close-code>the WebSocket connection
close code</a></i>, and whose <code title=dom-CloseEvent-reason><a href=#dom-closeevent-reason>reason</a></code> attribute is
initialized to <i><a href=#the-websocket-connection-close-reason>the WebSocket connection close reason</a></i> <a href=#decoded-as-utf-8,-with-error-handling>decoded as UTF-8, with error
- handling</a>, and dispatch the event at the <code><a href=#websocket>WebSocket</a></code> object. <a href=#refsWSP>[WSP]</a></li>
+ handling</a>, and <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> the event at the
+ <code><a href=#websocket>WebSocket</a></code> object. <a href=#refsWSP>[WSP]</a></li>
</ol><div class=warning>
@@ -86019,10 +85970,10 @@
<li>
- <p><a href=#queue-a-task>Queue a task</a> to dispatch the event created in the
- previous step at the <code><a href=#window>Window</a></code> object on which the
- method was invoked. The <a href=#task-source>task source</a> for this <a href=#concept-task title=concept-task>task</a> is the <a href=#posted-message-task-source>posted message task
- source</a>.</p>
+ <p><a href=#queue-a-task>Queue a task</a> to <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> the event
+ created in the previous step at the <code><a href=#window>Window</a></code> object on which the method was invoked.
+ The <a href=#task-source>task source</a> for this <a href=#concept-task title=concept-task>task</a> is the <a href=#posted-message-task-source>posted
+ message task source</a>.</p>
</li>
@@ -87191,12 +87142,10 @@
storage</a>, <a href=#localStorageEvent>for local
storage</a>).</p>
- <p>When this happens, the user agent must <a href=#queue-a-task>queue a task</a>
- to fire an event with the name <code><a href=#storage-0>storage</a></code>, which does not
- bubble and is not cancelable, and which uses the
- <code><a href=#storageevent>StorageEvent</a></code> interface, at each <code><a href=#window>Window</a></code>
- object whose <code><a href=#document>Document</a></code> object has a <code><a href=#storage-0>Storage</a></code>
- object that is affected.</p>
+ <p>When this happens, the user agent must <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event
+ with the name <code><a href=#storage-0>storage</a></code>, which does not bubble and is not cancelable, and which uses
+ the <code><a href=#storageevent>StorageEvent</a></code> interface, at each <code><a href=#window>Window</a></code> object whose
+ <code><a href=#document>Document</a></code> object has a <code><a href=#storage-0>Storage</a></code> object that is affected.</p>
<p class=note>This includes <code><a href=#document>Document</a></code> objects that are
not <a href=#fully-active>fully active</a>, but events fired on those are ignored
@@ -95852,14 +95801,11 @@
<li><p>Set the <code><a href=#document>Document</a></code>'s <a href=#page-showing>page showing</a>
flag to true.</li>
- <li><p>Fire a <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code> event
- at the <code><a href=#window>Window</a></code> object of the <code><a href=#document>Document</a></code>,
- but with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to
- the <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the
- <code><a href=#window>Window</a></code> object), using the
- <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface, with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code>
- attribute initialized to false. This event must not bubble, must
- not be cancelable, and has no default action.</li>
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code> at the <code><a href=#window>Window</a></code> object of the
+ <code><a href=#document>Document</a></code>, but with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to the
+ <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the <code><a href=#window>Window</a></code> object),
+ using the <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface, with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code> attribute initialized to false. This
+ event must not bubble, must not be cancelable, and has no default action.</li>
</ol></li>
Modified: index
===================================================================
--- index 2012-11-05 21:05:36 UTC (rev 7505)
+++ index 2012-11-05 21:38:04 UTC (rev 7506)
@@ -3468,13 +3468,12 @@
operate on the actual underlying data, not a snapshot of the
data.</p>
- <p>In the contexts of events, the terms <dfn title="">fire</dfn> and
- <dfn id=concept-event-dispatch title=concept-event-dispatch>dispatch</dfn> are used as
- defined in the DOM Core specification: firing an event means to
- create and dispatch it, and dispatching an event means to follow the
- steps that propagate the event through the tree. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is used to refer
- to events whose <code title=dom-event-isTrusted><a href=#dom-event-istrusted>isTrusted</a></code>
- attribute is initialized to true. <a href=#refsDOMCORE>[DOMCORE]</a></p>
+ <p>In the contexts of events, the terms <i>fire</i> and <i>dispatch</i> are used as defined in the
+ DOM Core specification: <dfn id=concept-event-fire title=concept-event-fire>firing</dfn> an event means to create and
+ <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> it, and <dfn id=concept-event-dispatch title=concept-event-dispatch>dispatching</dfn> an event means to follow the steps that propagate
+ the event through the tree. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is
+ used to refer to events whose <code title=dom-event-isTrusted><a href=#dom-event-istrusted>isTrusted</a></code> attribute is
+ initialized to true. <a href=#refsDOMCORE>[DOMCORE]</a></p>
<h4 id=plugins><span class=secno>2.1.5 </span>Plugins</h4>
@@ -12816,8 +12815,7 @@
<li>
- <p>Dispatch the required <code title=event-click><a href=#event-click>click</a></code>
- event.</p> <!-- interaction event spec point -->
+ <p><a href=#concept-event-dispatch title=concept-event-dispatch>Dispatch</a> the required <code title=event-click><a href=#event-click>click</a></code> event.</p> <!-- interaction event spec point -->
<p>If there is an element <var title="">e</var> and the <code title=event-click><a href=#event-click>click</a></code> event is not canceled, <a href=#run-post-click-activation-steps>run
post-click activation steps</a> on element <var title="">e</var>.</p>
@@ -30108,11 +30106,9 @@
<code><a href=#audiotracklist>AudioTrackList</a></code> object with the new
<code><a href=#audiotrack>AudioTrack</a></code> object.</li>
- <li><p>Fire an event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and
- is not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized
- to the new <code><a href=#audiotrack>AudioTrack</a></code> object, at this
- <code><a href=#audiotracklist>AudioTrackList</a></code> object.</li>
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to the new
+ <code><a href=#audiotrack>AudioTrack</a></code> object, at this <code><a href=#audiotracklist>AudioTrackList</a></code> object.</li>
</ol></dd>
@@ -30129,11 +30125,9 @@
<code><a href=#videotracklist>VideoTrackList</a></code> object with the new
<code><a href=#videotrack>VideoTrack</a></code> object.</li>
- <li><p>Fire an event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and
- is not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized
- to the new <code><a href=#videotrack>VideoTrack</a></code> object, at this
- <code><a href=#videotracklist>VideoTrackList</a></code> object.</li>
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to the new
+ <code><a href=#videotrack>VideoTrack</a></code> object, at this <code><a href=#videotracklist>VideoTrackList</a></code> object.</li>
</ol></dd>
@@ -30819,23 +30813,17 @@
<!-- see https://www.w3.org/Bugs/Public/show_bug.cgi?id=14492 -->
<!-- basically this is to handle very-long-running streams that use
different video and audio tracks per TV show -->
- <p>If at any time the user agent learns that an audio or video track
- has ended and all <a href=#media-data>media data</a> relating to that track
- corresponds to parts of the <a href=#media-timeline>media timeline</a> that are
- <em>before</em> the <a href=#earliest-possible-position>earliest possible position</a>, the
- user agent may <a href=#queue-a-task>queue a task</a> to remove the track from
- the <code title=dom-media-audioTracks><a href=#dom-media-audiotracks>audioTracks</a></code>
- attribute's <code><a href=#audiotracklist>AudioTrackList</a></code> object or the <code title=dom-media-videoTracks><a href=#dom-media-videotracks>videoTracks</a></code> attribute's
- <code><a href=#videotracklist>VideoTrackList</a></code> object as appropriate and then fire an
- event with the name <code title=event-removetrack>removetrack</code>, that does not bubble
- and is not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code>
- attribute initialized to the <code><a href=#audiotrack>AudioTrack</a></code> or
- <code><a href=#videotrack>VideoTrack</a></code> object representing the track, at the
- <a href=#media-element>media element</a>'s aforementioned
- <code><a href=#audiotracklist>AudioTrackList</a></code> or <code><a href=#videotracklist>VideoTrackList</a></code>
- object.</p>
+ <p>If at any time the user agent learns that an audio or video track has ended and all <a href=#media-data>media
+ data</a> relating to that track corresponds to parts of the <a href=#media-timeline>media timeline</a> that
+ are <em>before</em> the <a href=#earliest-possible-position>earliest possible position</a>, the user agent may <a href=#queue-a-task>queue a
+ task</a> to remove the track from the <code title=dom-media-audioTracks><a href=#dom-media-audiotracks>audioTracks</a></code>
+ attribute's <code><a href=#audiotracklist>AudioTrackList</a></code> object or the <code title=dom-media-videoTracks><a href=#dom-media-videotracks>videoTracks</a></code> attribute's <code><a href=#videotracklist>VideoTrackList</a></code> object as
+ appropriate and then <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-removetrack>removetrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to the <code><a href=#audiotrack>AudioTrack</a></code> or
+ <code><a href=#videotrack>VideoTrack</a></code> object representing the track, at the <a href=#media-element>media element</a>'s
+ aforementioned <code><a href=#audiotracklist>AudioTrackList</a></code> or <code><a href=#videotracklist>VideoTrackList</a></code> object.</p>
+
<p>The <dfn id=dom-media-duration title=dom-media-duration><code>duration</code></dfn>
attribute must return the time of the end of the <a href=#media-resource>media
resource</a>, in seconds, on the <a href=#media-timeline>media timeline</a>. If
@@ -34160,12 +34148,10 @@
<li><p>Add the new <a href=#text-track>text track</a> to the <a href=#media-element>media
element</a>'s <a href=#list-of-text-tracks>list of text tracks</a>.</li>
- <li><p>Fire an event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is
- not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code>
- attribute initialized to the <a href=#text-track>text track</a>'s
- <code><a href=#texttrack>TextTrack</a></code> object, at the <a href=#media-element>media element</a>'s
- <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is not cancelable, and that uses
+ the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code>
+ attribute initialized to the <a href=#text-track>text track</a>'s <code><a href=#texttrack>TextTrack</a></code> object, at the
+ <a href=#media-element>media element</a>'s <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's
<code><a href=#texttracklist>TextTrackList</a></code> object.</li>
</ol><!-- removetrack: we don't currently ever remove an in-band text
@@ -34238,30 +34224,22 @@
<a href=#webvtt>WebVTT</a>, this is the <a href=#rules-for-updating-the-display-of-webvtt-text-tracks>rules for updating the
display of WebVTT text tracks</a>. <a href=#refsWEBVTT>[WEBVTT]</a></p>
- <p>When a <code><a href=#the-track-element>track</a></code> element's parent element changes and
- the new parent is a <a href=#media-element>media element</a>, then the user agent
- must add the <code><a href=#the-track-element>track</a></code> element's corresponding <a href=#text-track>text
- track</a> to the <a href=#media-element>media element</a>'s <a href=#list-of-text-tracks>list of text
- tracks</a>, and then <a href=#queue-a-task>queue a task</a> to fire an event
- with the name <code title=event-addtrack>addtrack</code>, that
- does not bubble and is not cancelable, and that uses the
- <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to
- the <a href=#text-track>text track</a>'s <code><a href=#texttrack>TextTrack</a></code> object, at the
+ <p>When a <code><a href=#the-track-element>track</a></code> element's parent element changes and the new parent is a <a href=#media-element>media
+ element</a>, then the user agent must add the <code><a href=#the-track-element>track</a></code> element's corresponding
+ <a href=#text-track>text track</a> to the <a href=#media-element>media element</a>'s <a href=#list-of-text-tracks>list of text tracks</a>, and
+ then <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is not cancelable, and that uses
+ the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code>
+ attribute initialized to the <a href=#text-track>text track</a>'s <code><a href=#texttrack>TextTrack</a></code> object, at the
<a href=#media-element>media element</a>'s <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's
<code><a href=#texttracklist>TextTrackList</a></code> object.</p>
- <p>When a <code><a href=#the-track-element>track</a></code> element's parent element changes and
- the old parent was a <a href=#media-element>media element</a>, then the user agent
- must remove the <code><a href=#the-track-element>track</a></code> element's corresponding
- <a href=#text-track>text track</a> from the <a href=#media-element>media element</a>'s
- <a href=#list-of-text-tracks>list of text tracks</a>, and then <a href=#queue-a-task>queue a task</a>
- to fire an event with the name <code title=event-removetrack>removetrack</code>, that does not bubble
- and is not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code>
- attribute initialized to the <a href=#text-track>text track</a>'s
- <code><a href=#texttrack>TextTrack</a></code> object, at the <a href=#media-element>media element</a>'s
- <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's
- <code><a href=#texttracklist>TextTrackList</a></code> object.</p> <!-- removetrack -->
+ <p>When a <code><a href=#the-track-element>track</a></code> element's parent element changes and the old parent was a <a href=#media-element>media
+ element</a>, then the user agent must remove the <code><a href=#the-track-element>track</a></code> element's corresponding
+ <a href=#text-track>text track</a> from the <a href=#media-element>media element</a>'s <a href=#list-of-text-tracks>list of text tracks</a>,
+ and then <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-removetrack>removetrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to the <a href=#text-track>text track</a>'s
+ <code><a href=#texttrack>TextTrack</a></code> object, at the <a href=#media-element>media element</a>'s <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's <code><a href=#texttracklist>TextTrackList</a></code> object.</p>
+ <!-- removetrack -->
<hr><p>When a <a href=#text-track>text track</a> corresponding to a
<code><a href=#the-track-element>track</a></code> element is added to a <a href=#media-element>media
@@ -34821,12 +34799,10 @@
<li>
- <p><a href=#queue-a-task>Queue a task</a> to fire an event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and
- is not cancelable, and that uses the <code><a href=#trackevent>TrackEvent</a></code>
- interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to
- the new <a href=#text-track>text track</a>'s <code><a href=#texttrack>TextTrack</a></code> object,
- at the <a href=#media-element>media element</a>'s <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's
- <code><a href=#texttracklist>TextTrackList</a></code> object.</p>
+ <p><a href=#queue-a-task>Queue a task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-addtrack>addtrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code><a href=#trackevent>TrackEvent</a></code> interface, with the <code title=dom-TrackEvent-track><a href=#dom-trackevent-track>track</a></code> attribute initialized to the new <a href=#text-track>text
+ track</a>'s <code><a href=#texttrack>TextTrack</a></code> object, at the <a href=#media-element>media element</a>'s <code title=dom-media-textTracks><a href=#dom-media-texttracks>textTracks</a></code> attribute's <code><a href=#texttracklist>TextTrackList</a></code>
+ object.</p>
</li>
@@ -59164,13 +59140,11 @@
<dl class=switch><dt>If the user requested a context menu using a pointing device</dt>
- <dd><p>The user agent must fire an event with the name <code title=event-contextmenu>contextmenu</code>, that bubbles and is
- cancelable, and that uses the <code><a href=#mouseevent>MouseEvent</a></code> interface, at
- the element for which the menu was requested. The context
- information of the event must be initialized to the same values as
- the last <code><a href=#mouseevent>MouseEvent</a></code> user interaction event that was
- fired as part of the gesture that that was interpreted as a request
- for the context menu.</dd>
+ <dd><p>The user agent must <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-contextmenu>contextmenu</code>, that bubbles and is cancelable, and that uses the
+ <code><a href=#mouseevent>MouseEvent</a></code> interface, at the element for which the menu was requested. The context
+ information of the event must be initialized to the same values as the last
+ <code><a href=#mouseevent>MouseEvent</a></code> user interaction event that was fired as part of the gesture that that
+ was interpreted as a request for the context menu.</dd>
<dt>Otherwise</dt>
@@ -71435,14 +71409,11 @@
<li><p>Set the <code><a href=#document>Document</a></code>'s <a href=#page-showing>page
showing</a> flag to true.</li>
- <li><p>Fire a <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code>
- event at the <code><a href=#window>Window</a></code> object of that
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code> at the <code><a href=#window>Window</a></code> object of that
<code><a href=#document>Document</a></code>, but with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to the
- <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the
- <code><a href=#window>Window</a></code> object), using the
- <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface, with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code>
- attribute initialized to true. This event must not bubble, must
- not be cancelable, and has no default action.</li>
+ <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the <code><a href=#window>Window</a></code> object),
+ using the <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface, with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code> attribute initialized to true.
+ This event must not bubble, must not be cancelable, and has no default action.</li>
</ol><!-- an interesting thing to test would be to traverse back
during onload, before the first pageshow has fired, and then to
@@ -71504,19 +71475,17 @@
<code><a href=#document>Document</a></code> of the <var title="">specified entry</var> be
the <var title="">specified entry</var>.</li>
- <li><p>If <var title="">state changed</var> is true, fire a <code title=event-popstate><a href=#event-popstate>popstate</a></code> event at the
- <code><a href=#window>Window</a></code> object of the <code><a href=#document>Document</a></code>, using the
- <code><a href=#popstateevent>PopStateEvent</a></code> interface, with the <code title=dom-PopStateEvent-state><a href=#dom-popstateevent-state>state</a></code> attribute initialized
- to the value of <var title="">state</var>. This event must bubble
- but not be cancelable and has no default action.</li>
+ <li><p>If <var title="">state changed</var> is true, <a href=#concept-event-fire title=concept-event-fire>fire</a>
+ a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-popstate><a href=#event-popstate>popstate</a></code> at the <code><a href=#window>Window</a></code> object of the
+ <code><a href=#document>Document</a></code>, using the <code><a href=#popstateevent>PopStateEvent</a></code> interface, with the <code title=dom-PopStateEvent-state><a href=#dom-popstateevent-state>state</a></code> attribute initialized to the value of <var title="">state</var>. This event must bubble but not be cancelable and has no default
+ action.</li>
- <li><p>If <var title="">hash changed</var> is true, then fire a
- <code title=event-hashchange><a href=#event-hashchange>hashchange</a></code> event at the
- <a href=#browsing-context>browsing context</a>'s <code><a href=#window>Window</a></code> object, using
- the <code><a href=#hashchangeevent>HashChangeEvent</a></code> interface, with the <code title=dom-HashChangeEvent-oldURL><a href=#dom-hashchangeevent-oldurl>oldURL</a></code> attribute
- initialized to <var title="">old URL</var> and the <code title=dom-HashChangeEvent-newURL><a href=#dom-hashchangeevent-newurl>newURL</a></code> attribute
- initialized to <var title="">new URL</var>. This event must bubble
- but not be cancelable and has no default action.</li>
+ <li><p>If <var title="">hash changed</var> is true, then <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>
+ event with the name <code title=event-hashchange><a href=#event-hashchange>hashchange</a></code> at the <a href=#browsing-context>browsing
+ context</a>'s <code><a href=#window>Window</a></code> object, using the <code><a href=#hashchangeevent>HashChangeEvent</a></code> interface,
+ with the <code title=dom-HashChangeEvent-oldURL><a href=#dom-hashchangeevent-oldurl>oldURL</a></code> attribute initialized to <var title="">old URL</var> and the <code title=dom-HashChangeEvent-newURL><a href=#dom-hashchangeevent-newurl>newURL</a></code> attribute
+ initialized to <var title="">new URL</var>. This event must bubble but not be cancelable and has
+ no default action.</li>
<li><p>The <a href=#current-entry>current entry</a> is now the <var title="">specified entry</var>.</li>
@@ -71674,8 +71643,7 @@
<li><p>Let <var title="">event</var> be a new <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>
<code><a href=#beforeunloadevent>BeforeUnloadEvent</a></code> event object with the name <code title=event-beforeunload>beforeunload</code>, which does not bubble but is cancelable.</li>
- <li><p><i>Dispatch</i>: Dispatch <var title="">event</var> at the
- <code><a href=#document>Document</a></code>'s <code><a href=#window>Window</a></code> object.</li>
+ <li><p><i>Dispatch</i>: <a href=#concept-event-dispatch title=concept-event-dispatch>Dispatch</a> <var title="">event</var> at the <code><a href=#document>Document</a></code>'s <code><a href=#window>Window</a></code> object.</li>
<li><p>Decrease the <a href=#event-loop>event loop</a>'s <a href=#termination-nesting-level>termination
nesting level</a> by one.</li>
@@ -71759,14 +71727,12 @@
<li><p>Set the <code><a href=#document>Document</a></code>'s <a href=#page-showing>page showing</a>
flag to false.</li>
- <li><p>Fire a <code title=event-pagehide><a href=#event-pagehide>pagehide</a></code> event at
- the <code><a href=#window>Window</a></code> object of the <code><a href=#document>Document</a></code>, but
- with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to the
- <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the
- <code><a href=#window>Window</a></code> object), using the
- <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface, with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code>
- attribute initialized to true. This event must not bubble, must not
- be cancelable, and has no default action.</li>
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-pagehide><a href=#event-pagehide>pagehide</a></code> at the <code><a href=#window>Window</a></code> object of the
+ <code><a href=#document>Document</a></code>, but with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to the
+ <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code>
+ set to the <code><a href=#window>Window</a></code> object), using the <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface,
+ with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code> attribute initialized
+ to true. This event must not bubble, must not be cancelable, and has no default action.</li>
<li>
@@ -73348,23 +73314,17 @@
</li>
- <li><p>For each <a href=#cache-host>cache host</a> associated with an
- <a href=#application-cache>application cache</a> in <var title="">cache
- group</var>, <a href=#queue-a-post-load-task>queue a post-load task</a> to fire an event
- with the name <code title=event-appcache-progress><a href=#event-appcache-progress>progress</a></code>, which does not
- bubble, which is cancelable, and which uses the
- <code>ProgressEvent</code> interface, at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
- host</a>. The <code title=dom-ProgressEvents-lengthComputable>lengthComputable</code>
- attribute must be set to true, the <code title=dom-ProgressEvents-total>total</code> attribute must be
- set to the number of files in <var title="">file list</var>, and
- the <code title=dom-ProgressEvents-loaded>loaded</code>
- attribute must be set to the number of files in <var title="">file list</var> that have been either downloaded or
- skipped so far. The default action of these events must be, if
- the user agent <a href=#shows-caching-progress>shows caching progress</a>, the display
- of some sort of user interface indicating to the user that a file
- is being downloaded in preparation for updating the application.
- <a href=#refsPROGRESS>[PROGRESS]</a></li>
+ <li><p>For each <a href=#cache-host>cache host</a> associated with an <a href=#application-cache>application cache</a> in
+ <var title="">cache group</var>, <a href=#queue-a-post-load-task>queue a post-load task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>
+ event with the name <code title=event-appcache-progress><a href=#event-appcache-progress>progress</a></code>, which does not
+ bubble, which is cancelable, and which uses the <code>ProgressEvent</code> interface, at the
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache host</a>. The <code title=dom-ProgressEvents-lengthComputable>lengthComputable</code> attribute must be set to
+ true, the <code title=dom-ProgressEvents-total>total</code> attribute must be set to the
+ number of files in <var title="">file list</var>, and the <code title=dom-ProgressEvents-loaded>loaded</code> attribute must be set to the number of files in
+ <var title="">file list</var> that have been either downloaded or skipped so far. The default
+ action of these events must be, if the user agent <a href=#shows-caching-progress>shows caching progress</a>, the
+ display of some sort of user interface indicating to the user that a file is being downloaded
+ in preparation for updating the application. <a href=#refsPROGRESS>[PROGRESS]</a></li>
<li>
@@ -73499,20 +73459,14 @@
</ol></li>
- <li><p>For each <a href=#cache-host>cache host</a> associated with an
- <a href=#application-cache>application cache</a> in <var title="">cache group</var>,
- <a href=#queue-a-post-load-task>queue a post-load task</a> to fire an event with the name
- <code title=event-appcache-progress><a href=#event-appcache-progress>progress</a></code>, which does
- not bubble, which is cancelable, and which uses the
- <code>ProgressEvent</code> interface, at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
- host</a>. The <code title=dom-ProgressEvents-lengthComputable>lengthComputable</code>
- attribute must be set to true, the <code title=dom-ProgressEvents-total>total</code> and the <code title=dom-ProgressEvents-loaded>loaded</code> attributes must be
- set to the number of files in <var title="">file list</var>. The
- default action of these events must be, if the user agent
- <a href=#shows-caching-progress>shows caching progress</a>, the display of some sort of
- user interface indicating to the user that all the files have been
- downloaded. <a href=#refsPROGRESS>[PROGRESS]</a></li>
+ <li><p>For each <a href=#cache-host>cache host</a> associated with an <a href=#application-cache>application cache</a> in <var title="">cache group</var>, <a href=#queue-a-post-load-task>queue a post-load task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a>
+ event with the name <code title=event-appcache-progress><a href=#event-appcache-progress>progress</a></code>, which does not bubble,
+ which is cancelable, and which uses the <code>ProgressEvent</code> interface, at the
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache host</a>. The <code title=dom-ProgressEvents-lengthComputable>lengthComputable</code> attribute must be set to
+ true, the <code title=dom-ProgressEvents-total>total</code> and the <code title=dom-ProgressEvents-loaded>loaded</code> attributes must be set to the number of files in
+ <var title="">file list</var>. The default action of these events must be, if the user agent
+ <a href=#shows-caching-progress>shows caching progress</a>, the display of some sort of user interface indicating to the
+ user that all the files have been downloaded. <a href=#refsPROGRESS>[PROGRESS]</a></li>
<li><p>Store the list of <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback namespaces</a>,
and the URLs of the <a href=#concept-appcache-fallback title=concept-appcache-fallback>fallback entries</a> that they
@@ -74972,11 +74926,10 @@
of related similar-origin browsing contexts</a> to which the
<a href="#script's-browsing-context">script's browsing context</a> belongs.</p>
- <p class=note>This will typically fire scripted callbacks, which
- calls the <a href=#jump-to-a-code-entry-point>jump to a code entry-point</a> algorithm, which
- calls this <a href=#perform-a-microtask-checkpoint>perform a microtask checkpoint</a> algorithm
- again, which is why we use the <a href=#running-mutation-observers>running mutation
- observers</a> flag to avoid reentrancy.</p>
+ <p class=note>This will typically invoke scripted callbacks, which calls the <a href=#jump-to-a-code-entry-point>jump to a
+ code entry-point</a> algorithm, which calls this <a href=#perform-a-microtask-checkpoint>perform a microtask checkpoint</a>
+ algorithm again, which is why we use the <a href=#running-mutation-observers>running mutation observers</a> flag to avoid
+ reentrancy.</p>
</li>
@@ -80314,8 +80267,8 @@
</li>
- <li><p>Dispatch the newly created <code><a href=#dragevent>DragEvent</a></code> object at
- the specified target element.</li>
+ <li><p><a href=#concept-event-dispatch title=concept-event-dispatch>Dispatch</a> the newly created
+ <code><a href=#dragevent>DragEvent</a></code> object at the specified target element.</li>
<li><p>Set the <a href=#drag-data-store-allowed-effects-state>drag data store allowed effects state</a>
to the current value of <var title="">dataTransfer</var>'s <code title=dom-DataTransfer-effectAllowed><a href=#dom-datatransfer-effectallowed>effectAllowed</a></code>
@@ -80799,12 +80752,10 @@
<dd><p>Reset the <a href=#current-drag-operation>current drag operation</a> to "<code title="">none</code>".</dd>
- </dl><p>Otherwise (if the <code title=event-dragover><a href=#event-dragover>dragover</a></code> event <em>is</em>
- canceled), set the <a href=#current-drag-operation>current drag operation</a> based on
- the values of the <code title=dom-DataTransfer-effectAllowed><a href=#dom-datatransfer-effectallowed>effectAllowed</a></code> and
- <code title=dom-DataTransfer-dropEffect><a href=#dom-datatransfer-dropeffect>dropEffect</a></code>
- attributes of the <code><a href=#dragevent>DragEvent</a></code> object's <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code> object as
- they stood after the event dispatch finished, as per the
+ </dl><p>Otherwise (if the <code title=event-dragover><a href=#event-dragover>dragover</a></code> event <em>is</em> canceled),
+ set the <a href=#current-drag-operation>current drag operation</a> based on the values of the <code title=dom-DataTransfer-effectAllowed><a href=#dom-datatransfer-effectallowed>effectAllowed</a></code> and <code title=dom-DataTransfer-dropEffect><a href=#dom-datatransfer-dropeffect>dropEffect</a></code> attributes of the <code><a href=#dragevent>DragEvent</a></code>
+ object's <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code> object as they stood
+ after the event <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> finished, as per the
following table:</p>
<table><thead><tr><th><code title=dom-DataTransfer-effectAllowed><a href=#dom-datatransfer-effectallowed>effectAllowed</a></code></th>
@@ -80886,10 +80837,11 @@
<li>
- <p>If the event is canceled, set the <a href=#current-drag-operation>current drag
- operation</a> to the value of the <code title=dom-DataTransfer-dropEffect><a href=#dom-datatransfer-dropeffect>dropEffect</a></code> attribute
- of the <code><a href=#dragevent>DragEvent</a></code> object's <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code> object
- as it stood after the event dispatch finished.</p>
+ <p>If the event is canceled, set the <a href=#current-drag-operation>current drag operation</a> to the value of the
+ <code title=dom-DataTransfer-dropEffect><a href=#dom-datatransfer-dropeffect>dropEffect</a></code> attribute of the
+ <code><a href=#dragevent>DragEvent</a></code> object's <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code>
+ object as it stood after the event <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a>
+ finished.</p>
<p>Otherwise, the event is not canceled; perform the event's
default action, which depends on the exact target as
@@ -83145,16 +83097,15 @@
may be reported to the user.
</p>
- <p>For dedicated workers, if the error is still <i title=concept-error-nothandled><a href=#concept-error-nothandled>not handled</a></i> afterwards, or if
- the error occurred while handling a previous script error, the user
- agent must <a href=#queue-a-task>queue a task</a> to fire an event that uses the
- <code><a href=#errorevent>ErrorEvent</a></code> interface, with the name <code title=event-error>error</code>, that doesn't bubble and is
- cancelable, with its <code title=dom-ErrorEvent-message><a href=#dom-errorevent-message>message</a></code>, <code title=dom-ErrorEvent-filename><a href=#dom-errorevent-filename>filename</a></code>, <code title=dom-ErrorEvent-lineno><a href=#dom-errorevent-lineno>lineno</a></code>, and <code title=dom-ErrorEvent-column><a href=#dom-errorevent-column>column</a></code> attributes initialized
- appropriately, at the <code><a href=#worker>Worker</a></code> object associated with the
- worker. If the event is not canceled, the user agent must act as if
- the uncaught runtime script error had occurred in the global scope
- that the <code><a href=#worker>Worker</a></code> object is in, thus repeating the entire
- runtime script error reporting process one level up.</p>
+ <p>For dedicated workers, if the error is still <i title=concept-error-nothandled><a href=#concept-error-nothandled>not
+ handled</a></i> afterwards, or if the error occurred while handling a previous script error, the user
+ agent must <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event that uses the <code><a href=#errorevent>ErrorEvent</a></code>
+ interface, with the name <code title=event-error>error</code>, that doesn't bubble and is
+ cancelable, with its <code title=dom-ErrorEvent-message><a href=#dom-errorevent-message>message</a></code>, <code title=dom-ErrorEvent-filename><a href=#dom-errorevent-filename>filename</a></code>, <code title=dom-ErrorEvent-lineno><a href=#dom-errorevent-lineno>lineno</a></code>, and <code title=dom-ErrorEvent-column><a href=#dom-errorevent-column>column</a></code>
+ attributes initialized appropriately, at the <code><a href=#worker>Worker</a></code> object associated with the
+ worker. If the event is not canceled, the user agent must act as if the uncaught runtime script
+ error had occurred in the global scope that the <code><a href=#worker>Worker</a></code> object is in, thus repeating
+ the entire runtime script error reporting process one level up.</p>
<p>If the implicit port connecting the worker to its
<code><a href=#worker>Worker</a></code> object has been disentangled (i.e. if the parent
@@ -83529,7 +83480,8 @@
is initialized to the empty string, has a <code title=dom-MessageEvent-ports><a href=#dom-messageevent-ports>ports</a></code>
attribute whose value is initialized to a <a href=#dfn-read-only-array title=dfn-read-only-array>read only</a>
array containing only the newly created port, and has a <code title=dom-MessageEvent-source><a href=#dom-messageevent-source>source</a></code> attribute whose value is initialized to the
- newly created port, and <a href=#queue-a-task>queue a task</a> to dispatch the event at <var title="">worker global scope</var>.</li>
+ newly created port, and <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> the event at <var title="">worker global
+ scope</var>.</li>
<li>
@@ -83584,8 +83536,8 @@
string, has a <code title=dom-MessageEvent-ports><a href=#dom-messageevent-ports>ports</a></code> attribute whose value is
initialized to a <a href=#dfn-read-only-array title=dfn-read-only-array>read only</a> array containing only the
newly created port, and has a <code title=dom-MessageEvent-source><a href=#dom-messageevent-source>source</a></code> attribute whose
- value is initialized to the newly created port, and <a href=#queue-a-task>queue a task</a> to dispatch the
- event at <var title="">worker global scope</var>.</li>
+ value is initialized to the newly created port, and <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> the event at <var title="">worker global
+ scope</var>.</li>
<li>
@@ -84520,12 +84472,10 @@
<li><p>Set the <var title="">data</var> buffer and the <var title="">event type</var> buffer to the empty string.</li>
- <li><p><a href=#queue-a-task>Queue a task</a> which, if the <code title=dom-EventSource-readyState><a href=#dom-eventsource-readystate>readyState</a></code> attribute is
- set to a value other than <code title=dom-EventSource-CLOSED><a href=#dom-eventsource-closed>CLOSED</a></code>, dispatches the newly
- created event at the <code><a href=#eventsource>EventSource</a></code> object.</li> <!--
- so calling close() drops the messages immediately. The connection
- dying doesn't interfere with already-sent messages since it sets us
- to CLOSED via a task, not synchronously -->
+ <li><p><a href=#queue-a-task>Queue a task</a> which, if the <code title=dom-EventSource-readyState><a href=#dom-eventsource-readystate>readyState</a></code> attribute is set to a value other than <code title=dom-EventSource-CLOSED><a href=#dom-eventsource-closed>CLOSED</a></code>, <a href=#concept-event-dispatch title=concept-event-dispatch>dispatches</a> the newly created event at the
+ <code><a href=#eventsource>EventSource</a></code> object.</li> <!-- so calling close() drops the messages immediately.
+ The connection dying doesn't interfere with already-sent messages since it sets us to CLOSED via
+ a task, not synchronously -->
</ol><p class=note>If an event doesn't have an "id" field, but an
earlier event did set the event source's <a href=#concept-event-stream-last-event-id title=concept-event-stream-last-event-id>last event ID
@@ -85417,7 +85367,7 @@
<li>
- <p>Dispatch <var title="">event</var> at the
+ <p><a href=#concept-event-dispatch title=concept-event-dispatch>Dispatch</a> <var title="">event</var> at the
<code><a href=#websocket>WebSocket</a></code> object.</p>
</li>
@@ -85478,7 +85428,8 @@
true if the connection closed <i title="">cleanly</i> and false otherwise, whose <code title=dom-CloseEvent-code><a href=#dom-closeevent-code>code</a></code> attribute is initialized to <i><a href=#the-websocket-connection-close-code>the WebSocket connection
close code</a></i>, and whose <code title=dom-CloseEvent-reason><a href=#dom-closeevent-reason>reason</a></code> attribute is
initialized to <i><a href=#the-websocket-connection-close-reason>the WebSocket connection close reason</a></i> <a href=#decoded-as-utf-8,-with-error-handling>decoded as UTF-8, with error
- handling</a>, and dispatch the event at the <code><a href=#websocket>WebSocket</a></code> object. <a href=#refsWSP>[WSP]</a></li>
+ handling</a>, and <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> the event at the
+ <code><a href=#websocket>WebSocket</a></code> object. <a href=#refsWSP>[WSP]</a></li>
</ol><div class=warning>
@@ -86019,10 +85970,10 @@
<li>
- <p><a href=#queue-a-task>Queue a task</a> to dispatch the event created in the
- previous step at the <code><a href=#window>Window</a></code> object on which the
- method was invoked. The <a href=#task-source>task source</a> for this <a href=#concept-task title=concept-task>task</a> is the <a href=#posted-message-task-source>posted message task
- source</a>.</p>
+ <p><a href=#queue-a-task>Queue a task</a> to <a href=#concept-event-dispatch title=concept-event-dispatch>dispatch</a> the event
+ created in the previous step at the <code><a href=#window>Window</a></code> object on which the method was invoked.
+ The <a href=#task-source>task source</a> for this <a href=#concept-task title=concept-task>task</a> is the <a href=#posted-message-task-source>posted
+ message task source</a>.</p>
</li>
@@ -87191,12 +87142,10 @@
storage</a>, <a href=#localStorageEvent>for local
storage</a>).</p>
- <p>When this happens, the user agent must <a href=#queue-a-task>queue a task</a>
- to fire an event with the name <code><a href=#storage-0>storage</a></code>, which does not
- bubble and is not cancelable, and which uses the
- <code><a href=#storageevent>StorageEvent</a></code> interface, at each <code><a href=#window>Window</a></code>
- object whose <code><a href=#document>Document</a></code> object has a <code><a href=#storage-0>Storage</a></code>
- object that is affected.</p>
+ <p>When this happens, the user agent must <a href=#queue-a-task>queue a task</a> to <a href=#concept-event-fire title=concept-event-fire>fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event
+ with the name <code><a href=#storage-0>storage</a></code>, which does not bubble and is not cancelable, and which uses
+ the <code><a href=#storageevent>StorageEvent</a></code> interface, at each <code><a href=#window>Window</a></code> object whose
+ <code><a href=#document>Document</a></code> object has a <code><a href=#storage-0>Storage</a></code> object that is affected.</p>
<p class=note>This includes <code><a href=#document>Document</a></code> objects that are
not <a href=#fully-active>fully active</a>, but events fired on those are ignored
@@ -95852,14 +95801,11 @@
<li><p>Set the <code><a href=#document>Document</a></code>'s <a href=#page-showing>page showing</a>
flag to true.</li>
- <li><p>Fire a <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code> event
- at the <code><a href=#window>Window</a></code> object of the <code><a href=#document>Document</a></code>,
- but with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to
- the <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the
- <code><a href=#window>Window</a></code> object), using the
- <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface, with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code>
- attribute initialized to false. This event must not bubble, must
- not be cancelable, and has no default action.</li>
+ <li><p><a href=#concept-event-fire title=concept-event-fire>Fire</a> a <a href=#concept-events-trusted title=concept-events-trusted>trusted</a> event with the name <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code> at the <code><a href=#window>Window</a></code> object of the
+ <code><a href=#document>Document</a></code>, but with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to the
+ <code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the <code><a href=#window>Window</a></code> object),
+ using the <code><a href=#pagetransitionevent>PageTransitionEvent</a></code> interface, with the <code title=dom-PageTransitionEvent-persisted><a href=#dom-pagetransitionevent-persisted>persisted</a></code> attribute initialized to false. This
+ event must not bubble, must not be cancelable, and has no default action.</li>
</ol></li>
Modified: source
===================================================================
--- source 2012-11-05 21:05:36 UTC (rev 7505)
+++ source 2012-11-05 21:38:04 UTC (rev 7506)
@@ -2348,15 +2348,13 @@
operate on the actual underlying data, not a snapshot of the
data.</p>
- <p>In the contexts of events, the terms <dfn title="">fire</dfn> and
- <dfn title="concept-event-dispatch">dispatch</dfn> are used as
- defined in the DOM Core specification: firing an event means to
- create and dispatch it, and dispatching an event means to follow the
- steps that propagate the event through the tree. The term <dfn
- title="concept-events-trusted">trusted event</dfn> is used to refer
- to events whose <code title="dom-event-isTrusted">isTrusted</code>
- attribute is initialized to true. <a
- href="#refsDOMCORE">[DOMCORE]</a></p>
+ <p>In the contexts of events, the terms <i>fire</i> and <i>dispatch</i> are used as defined in the
+ DOM Core specification: <dfn title="concept-event-fire">firing</dfn> an event means to create and
+ <span title="concept-event-dispatch">dispatch</span> it, and <dfn
+ title="concept-event-dispatch">dispatching</dfn> an event means to follow the steps that propagate
+ the event through the tree. The term <dfn title="concept-events-trusted">trusted event</dfn> is
+ used to refer to events whose <code title="dom-event-isTrusted">isTrusted</code> attribute is
+ initialized to true. <a href="#refsDOMCORE">[DOMCORE]</a></p>
<h4>Plugins</h4>
@@ -13379,8 +13377,8 @@
<li>
- <p>Dispatch the required <code title="event-click">click</code>
- event.</p> <!-- interaction event spec point -->
+ <p><span title="concept-event-dispatch">Dispatch</span> the required <code
+ title="event-click">click</code> event.</p> <!-- interaction event spec point -->
<p>If there is an element <var title="">e</var> and the <code
title="event-click">click</code> event is not canceled, <span>run
@@ -32692,13 +32690,12 @@
<code>AudioTrackList</code> object with the new
<code>AudioTrack</code> object.</p></li>
- <li><p>Fire an event with the name <code
- title="event-addtrack">addtrack</code>, that does not bubble and
- is not cancelable, and that uses the <code>TrackEvent</code>
- interface, with the <code
- title="dom-TrackEvent-track">track</code> attribute initialized
- to the new <code>AudioTrack</code> object, at this
- <code>AudioTrackList</code> object.</p></li>
+ <li><p><span title="concept-event-fire">Fire</span> a <span
+ title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-addtrack">addtrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code>TrackEvent</code> interface, with the <code
+ title="dom-TrackEvent-track">track</code> attribute initialized to the new
+ <code>AudioTrack</code> object, at this <code>AudioTrackList</code> object.</p></li>
</ol>
@@ -32720,13 +32717,12 @@
<code>VideoTrackList</code> object with the new
<code>VideoTrack</code> object.</p></li>
- <li><p>Fire an event with the name <code
- title="event-addtrack">addtrack</code>, that does not bubble and
- is not cancelable, and that uses the <code>TrackEvent</code>
- interface, with the <code
- title="dom-TrackEvent-track">track</code> attribute initialized
- to the new <code>VideoTrack</code> object, at this
- <code>VideoTrackList</code> object.</p></li>
+ <li><p><span title="concept-event-fire">Fire</span> a <span
+ title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-addtrack">addtrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code>TrackEvent</code> interface, with the <code
+ title="dom-TrackEvent-track">track</code> attribute initialized to the new
+ <code>VideoTrack</code> object, at this <code>VideoTrackList</code> object.</p></li>
</ol>
@@ -33541,24 +33537,20 @@
<!-- see https://www.w3.org/Bugs/Public/show_bug.cgi?id=14492 -->
<!-- basically this is to handle very-long-running streams that use
different video and audio tracks per TV show -->
- <p>If at any time the user agent learns that an audio or video track
- has ended and all <span>media data</span> relating to that track
- corresponds to parts of the <span>media timeline</span> that are
- <em>before</em> the <span>earliest possible position</span>, the
- user agent may <span>queue a task</span> to remove the track from
- the <code title="dom-media-audioTracks">audioTracks</code>
+
+ <p>If at any time the user agent learns that an audio or video track has ended and all <span>media
+ data</span> relating to that track corresponds to parts of the <span>media timeline</span> that
+ are <em>before</em> the <span>earliest possible position</span>, the user agent may <span>queue a
+ task</span> to remove the track from the <code title="dom-media-audioTracks">audioTracks</code>
attribute's <code>AudioTrackList</code> object or the <code
- title="dom-media-videoTracks">videoTracks</code> attribute's
- <code>VideoTrackList</code> object as appropriate and then fire an
- event with the name <code
- title="event-removetrack">removetrack</code>, that does not bubble
- and is not cancelable, and that uses the <code>TrackEvent</code>
- interface, with the <code title="dom-TrackEvent-track">track</code>
- attribute initialized to the <code>AudioTrack</code> or
- <code>VideoTrack</code> object representing the track, at the
- <span>media element</span>'s aforementioned
- <code>AudioTrackList</code> or <code>VideoTrackList</code>
- object.</p>
+ title="dom-media-videoTracks">videoTracks</code> attribute's <code>VideoTrackList</code> object as
+ appropriate and then <span title="concept-event-fire">fire</span> a <span
+ title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-removetrack">removetrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code>TrackEvent</code> interface, with the <code
+ title="dom-TrackEvent-track">track</code> attribute initialized to the <code>AudioTrack</code> or
+ <code>VideoTrack</code> object representing the track, at the <span>media element</span>'s
+ aforementioned <code>AudioTrackList</code> or <code>VideoTrackList</code> object.</p>
<p>The <dfn title="dom-media-duration"><code>duration</code></dfn>
attribute must return the time of the end of the <span>media
@@ -37421,13 +37413,12 @@
<li><p>Add the new <span>text track</span> to the <span>media
element</span>'s <span>list of text tracks</span>.</p></li>
- <li><p>Fire an event with the name <code
- title="event-addtrack">addtrack</code>, that does not bubble and is
- not cancelable, and that uses the <code>TrackEvent</code>
- interface, with the <code title="dom-TrackEvent-track">track</code>
- attribute initialized to the <span>text track</span>'s
- <code>TextTrack</code> object, at the <span>media element</span>'s
- <code title="dom-media-textTracks">textTracks</code> attribute's
+ <li><p><span title="concept-event-fire">Fire</span> a <span
+ title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-addtrack">addtrack</code>, that does not bubble and is not cancelable, and that uses
+ the <code>TrackEvent</code> interface, with the <code title="dom-TrackEvent-track">track</code>
+ attribute initialized to the <span>text track</span>'s <code>TextTrack</code> object, at the
+ <span>media element</span>'s <code title="dom-media-textTracks">textTracks</code> attribute's
<code>TextTrackList</code> object.</p></li>
</ol>
@@ -37518,33 +37509,28 @@
<span>WebVTT</span>, this is the <span>rules for updating the
display of WebVTT text tracks</span>. <a href="#refsWEBVTT">[WEBVTT]</a></p>
- <p>When a <code>track</code> element's parent element changes and
- the new parent is a <span>media element</span>, then the user agent
- must add the <code>track</code> element's corresponding <span>text
- track</span> to the <span>media element</span>'s <span>list of text
- tracks</span>, and then <span>queue a task</span> to fire an event
- with the name <code title="event-addtrack">addtrack</code>, that
- does not bubble and is not cancelable, and that uses the
- <code>TrackEvent</code> interface, with the <code
- title="dom-TrackEvent-track">track</code> attribute initialized to
- the <span>text track</span>'s <code>TextTrack</code> object, at the
- <span>media element</span>'s <code
- title="dom-media-textTracks">textTracks</code> attribute's
+ <p>When a <code>track</code> element's parent element changes and the new parent is a <span>media
+ element</span>, then the user agent must add the <code>track</code> element's corresponding
+ <span>text track</span> to the <span>media element</span>'s <span>list of text tracks</span>, and
+ then <span>queue a task</span> to <span title="concept-event-fire">fire</span> a <span
+ title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-addtrack">addtrack</code>, that does not bubble and is not cancelable, and that uses
+ the <code>TrackEvent</code> interface, with the <code title="dom-TrackEvent-track">track</code>
+ attribute initialized to the <span>text track</span>'s <code>TextTrack</code> object, at the
+ <span>media element</span>'s <code title="dom-media-textTracks">textTracks</code> attribute's
<code>TextTrackList</code> object.</p>
- <p>When a <code>track</code> element's parent element changes and
- the old parent was a <span>media element</span>, then the user agent
- must remove the <code>track</code> element's corresponding
- <span>text track</span> from the <span>media element</span>'s
- <span>list of text tracks</span>, and then <span>queue a task</span>
- to fire an event with the name <code
- title="event-removetrack">removetrack</code>, that does not bubble
- and is not cancelable, and that uses the <code>TrackEvent</code>
- interface, with the <code title="dom-TrackEvent-track">track</code>
- attribute initialized to the <span>text track</span>'s
- <code>TextTrack</code> object, at the <span>media element</span>'s
- <code title="dom-media-textTracks">textTracks</code> attribute's
- <code>TextTrackList</code> object.</p> <!-- removetrack -->
+ <p>When a <code>track</code> element's parent element changes and the old parent was a <span>media
+ element</span>, then the user agent must remove the <code>track</code> element's corresponding
+ <span>text track</span> from the <span>media element</span>'s <span>list of text tracks</span>,
+ and then <span>queue a task</span> to <span title="concept-event-fire">fire</span> a <span
+ title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-removetrack">removetrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code>TrackEvent</code> interface, with the <code
+ title="dom-TrackEvent-track">track</code> attribute initialized to the <span>text track</span>'s
+ <code>TextTrack</code> object, at the <span>media element</span>'s <code
+ title="dom-media-textTracks">textTracks</code> attribute's <code>TextTrackList</code> object.</p>
+ <!-- removetrack -->
<hr>
@@ -38187,15 +38173,14 @@
<li>
- <p><span>Queue a task</span> to fire an event with the name <code
- title="event-addtrack">addtrack</code>, that does not bubble and
- is not cancelable, and that uses the <code>TrackEvent</code>
- interface, with the <code
- title="dom-TrackEvent-track">track</code> attribute initialized to
- the new <span>text track</span>'s <code>TextTrack</code> object,
- at the <span>media element</span>'s <code
- title="dom-media-textTracks">textTracks</code> attribute's
- <code>TextTrackList</code> object.</p>
+ <p><span>Queue a task</span> to <span title="concept-event-fire">fire</span> a <span
+ title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-addtrack">addtrack</code>, that does not bubble and is not cancelable, and that
+ uses the <code>TrackEvent</code> interface, with the <code
+ title="dom-TrackEvent-track">track</code> attribute initialized to the new <span>text
+ track</span>'s <code>TextTrack</code> object, at the <span>media element</span>'s <code
+ title="dom-media-textTracks">textTracks</code> attribute's <code>TextTrackList</code>
+ object.</p>
</li>
@@ -69349,14 +69334,13 @@
<dt>If the user requested a context menu using a pointing device</dt>
- <dd><p>The user agent must fire an event with the name <code
- title="event-contextmenu">contextmenu</code>, that bubbles and is
- cancelable, and that uses the <code>MouseEvent</code> interface, at
- the element for which the menu was requested. The context
- information of the event must be initialized to the same values as
- the last <code>MouseEvent</code> user interaction event that was
- fired as part of the gesture that that was interpreted as a request
- for the context menu.</p></dd>
+ <dd><p>The user agent must <span title="concept-event-fire">fire</span> a <span
+ title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-contextmenu">contextmenu</code>, that bubbles and is cancelable, and that uses the
+ <code>MouseEvent</code> interface, at the element for which the menu was requested. The context
+ information of the event must be initialized to the same values as the last
+ <code>MouseEvent</code> user interaction event that was fired as part of the gesture that that
+ was interpreted as a request for the context menu.</p></dd>
<dt>Otherwise</dt>
@@ -83686,17 +83670,15 @@
<li><p>Set the <code>Document</code>'s <span>page
showing</span> flag to true.</p></li>
- <li><p>Fire a <code title="event-pageshow">pageshow</code>
- event at the <code>Window</code> object of that
- <code>Document</code>, but with its <code
- title="dom-event-target">target</code> set to the
+ <li><p><span title="concept-event-fire">Fire</span> a <span
+ title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-pageshow">pageshow</code> at the <code>Window</code> object of that
+ <code>Document</code>, but with its <code title="dom-event-target">target</code> set to the
<code>Document</code> object (and the <code
- title="dom-event-currentTarget">currentTarget</code> set to the
- <code>Window</code> object), using the
- <code>PageTransitionEvent</code> interface, with the <code
- title="dom-PageTransitionEvent-persisted">persisted</code>
- attribute initialized to true. This event must not bubble, must
- not be cancelable, and has no default action.</p></li>
+ title="dom-event-currentTarget">currentTarget</code> set to the <code>Window</code> object),
+ using the <code>PageTransitionEvent</code> interface, with the <code
+ title="dom-PageTransitionEvent-persisted">persisted</code> attribute initialized to true.
+ This event must not bubble, must not be cancelable, and has no default action.</p></li>
</ol>
@@ -83771,23 +83753,22 @@
<code>Document</code> of the <var title="">specified entry</var> be
the <var title="">specified entry</var>.</p></li>
- <li><p>If <var title="">state changed</var> is true, fire a <code
- title="event-popstate">popstate</code> event at the
- <code>Window</code> object of the <code>Document</code>, using the
- <code>PopStateEvent</code> interface, with the <code
- title="dom-PopStateEvent-state">state</code> attribute initialized
- to the value of <var title="">state</var>. This event must bubble
- but not be cancelable and has no default action.</p></li>
+ <li><p>If <var title="">state changed</var> is true, <span title="concept-event-fire">fire</span>
+ a <span title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-popstate">popstate</code> at the <code>Window</code> object of the
+ <code>Document</code>, using the <code>PopStateEvent</code> interface, with the <code
+ title="dom-PopStateEvent-state">state</code> attribute initialized to the value of <var
+ title="">state</var>. This event must bubble but not be cancelable and has no default
+ action.</p></li>
- <li><p>If <var title="">hash changed</var> is true, then fire a
- <code title="event-hashchange">hashchange</code> event at the
- <span>browsing context</span>'s <code>Window</code> object, using
- the <code>HashChangeEvent</code> interface, with the <code
- title="dom-HashChangeEvent-oldURL">oldURL</code> attribute
- initialized to <var title="">old URL</var> and the <code
- title="dom-HashChangeEvent-newURL">newURL</code> attribute
- initialized to <var title="">new URL</var>. This event must bubble
- but not be cancelable and has no default action.</p></li>
+ <li><p>If <var title="">hash changed</var> is true, then <span
+ title="concept-event-fire">fire</span> a <span title="concept-events-trusted">trusted</span>
+ event with the name <code title="event-hashchange">hashchange</code> at the <span>browsing
+ context</span>'s <code>Window</code> object, using the <code>HashChangeEvent</code> interface,
+ with the <code title="dom-HashChangeEvent-oldURL">oldURL</code> attribute initialized to <var
+ title="">old URL</var> and the <code title="dom-HashChangeEvent-newURL">newURL</code> attribute
+ initialized to <var title="">new URL</var>. This event must bubble but not be cancelable and has
+ no default action.</p></li>
<li><p>The <span>current entry</span> is now the <var
title="">specified entry</var>.</p></li>
@@ -83975,8 +83956,8 @@
<code>BeforeUnloadEvent</code> event object with the name <code
title="event-beforeunload">beforeunload</code>, which does not bubble but is cancelable.</p></li>
- <li><p><i>Dispatch</i>: Dispatch <var title="">event</var> at the
- <code>Document</code>'s <code>Window</code> object.</p></li>
+ <li><p><i>Dispatch</i>: <span title="concept-event-dispatch">Dispatch</span> <var
+ title="">event</var> at the <code>Document</code>'s <code>Window</code> object.</p></li>
<li><p>Decrease the <span>event loop</span>'s <span>termination
nesting level</span> by one.</p></li>
@@ -84076,16 +84057,14 @@
<li><p>Set the <code>Document</code>'s <span>page showing</span>
flag to false.</p></li>
- <li><p>Fire a <code title="event-pagehide">pagehide</code> event at
- the <code>Window</code> object of the <code>Document</code>, but
- with its <code title="dom-event-target">target</code> set to the
- <code>Document</code> object (and the <code
- title="dom-event-currentTarget">currentTarget</code> set to the
- <code>Window</code> object), using the
- <code>PageTransitionEvent</code> interface, with the <code
- title="dom-PageTransitionEvent-persisted">persisted</code>
- attribute initialized to true. This event must not bubble, must not
- be cancelable, and has no default action.</p></li>
+ <li><p><span title="concept-event-fire">Fire</span> a <span
+ title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-pagehide">pagehide</code> at the <code>Window</code> object of the
+ <code>Document</code>, but with its <code title="dom-event-target">target</code> set to the
+ <code>Document</code> object (and the <code title="dom-event-currentTarget">currentTarget</code>
+ set to the <code>Window</code> object), using the <code>PageTransitionEvent</code> interface,
+ with the <code title="dom-PageTransitionEvent-persisted">persisted</code> attribute initialized
+ to true. This event must not bubble, must not be cancelable, and has no default action.</p></li>
<li>
@@ -85930,27 +85909,20 @@
</li>
- <li><p>For each <span>cache host</span> associated with an
- <span>application cache</span> in <var title="">cache
- group</var>, <span>queue a post-load task</span> to fire an event
- with the name <code
- title="event-appcache-progress">progress</code>, which does not
- bubble, which is cancelable, and which uses the
- <code>ProgressEvent</code> interface, at the
- <code>ApplicationCache</code> singleton of the <span>cache
- host</span>. The <code
- title="dom-ProgressEvents-lengthComputable">lengthComputable</code>
- attribute must be set to true, the <code
- title="dom-ProgressEvents-total">total</code> attribute must be
- set to the number of files in <var title="">file list</var>, and
- the <code title="dom-ProgressEvents-loaded">loaded</code>
- attribute must be set to the number of files in <var
- title="">file list</var> that have been either downloaded or
- skipped so far. The default action of these events must be, if
- the user agent <span>shows caching progress</span>, the display
- of some sort of user interface indicating to the user that a file
- is being downloaded in preparation for updating the application.
- <a href="#refsPROGRESS">[PROGRESS]</a></p></li>
+ <li><p>For each <span>cache host</span> associated with an <span>application cache</span> in
+ <var title="">cache group</var>, <span>queue a post-load task</span> to <span
+ title="concept-event-fire">fire</span> a <span title="concept-events-trusted">trusted</span>
+ event with the name <code title="event-appcache-progress">progress</code>, which does not
+ bubble, which is cancelable, and which uses the <code>ProgressEvent</code> interface, at the
+ <code>ApplicationCache</code> singleton of the <span>cache host</span>. The <code
+ title="dom-ProgressEvents-lengthComputable">lengthComputable</code> attribute must be set to
+ true, the <code title="dom-ProgressEvents-total">total</code> attribute must be set to the
+ number of files in <var title="">file list</var>, and the <code
+ title="dom-ProgressEvents-loaded">loaded</code> attribute must be set to the number of files in
+ <var title="">file list</var> that have been either downloaded or skipped so far. The default
+ action of these events must be, if the user agent <span>shows caching progress</span>, the
+ display of some sort of user interface indicating to the user that a file is being downloaded
+ in preparation for updating the application. <a href="#refsPROGRESS">[PROGRESS]</a></p></li>
<li>
@@ -86097,23 +86069,18 @@
</li>
- <li><p>For each <span>cache host</span> associated with an
- <span>application cache</span> in <var title="">cache group</var>,
- <span>queue a post-load task</span> to fire an event with the name
- <code title="event-appcache-progress">progress</code>, which does
- not bubble, which is cancelable, and which uses the
- <code>ProgressEvent</code> interface, at the
- <code>ApplicationCache</code> singleton of the <span>cache
- host</span>. The <code
- title="dom-ProgressEvents-lengthComputable">lengthComputable</code>
- attribute must be set to true, the <code
- title="dom-ProgressEvents-total">total</code> and the <code
- title="dom-ProgressEvents-loaded">loaded</code> attributes must be
- set to the number of files in <var title="">file list</var>. The
- default action of these events must be, if the user agent
- <span>shows caching progress</span>, the display of some sort of
- user interface indicating to the user that all the files have been
- downloaded. <a href="#refsPROGRESS">[PROGRESS]</a></p></li>
+ <li><p>For each <span>cache host</span> associated with an <span>application cache</span> in <var
+ title="">cache group</var>, <span>queue a post-load task</span> to <span
+ title="concept-event-fire">fire</span> a <span title="concept-events-trusted">trusted</span>
+ event with the name <code title="event-appcache-progress">progress</code>, which does not bubble,
+ which is cancelable, and which uses the <code>ProgressEvent</code> interface, at the
+ <code>ApplicationCache</code> singleton of the <span>cache host</span>. The <code
+ title="dom-ProgressEvents-lengthComputable">lengthComputable</code> attribute must be set to
+ true, the <code title="dom-ProgressEvents-total">total</code> and the <code
+ title="dom-ProgressEvents-loaded">loaded</code> attributes must be set to the number of files in
+ <var title="">file list</var>. The default action of these events must be, if the user agent
+ <span>shows caching progress</span>, the display of some sort of user interface indicating to the
+ user that all the files have been downloaded. <a href="#refsPROGRESS">[PROGRESS]</a></p></li>
<li><p>Store the list of <span
title="concept-appcache-fallback-ns">fallback namespaces</span>,
@@ -87827,11 +87794,10 @@
of related similar-origin browsing contexts</span> to which the
<span>script's browsing context</span> belongs.</p>
- <p class="note">This will typically fire scripted callbacks, which
- calls the <span>jump to a code entry-point</span> algorithm, which
- calls this <span>perform a microtask checkpoint</span> algorithm
- again, which is why we use the <span>running mutation
- observers</span> flag to avoid reentrancy.</p>
+ <p class="note">This will typically invoke scripted callbacks, which calls the <span>jump to a
+ code entry-point</span> algorithm, which calls this <span>perform a microtask checkpoint</span>
+ algorithm again, which is why we use the <span>running mutation observers</span> flag to avoid
+ reentrancy.</p>
</li>
@@ -94048,8 +94014,8 @@
</li>
- <li><p>Dispatch the newly created <code>DragEvent</code> object at
- the specified target element.</p></li>
+ <li><p><span title="concept-event-dispatch">Dispatch</span> the newly created
+ <code>DragEvent</code> object at the specified target element.</p></li>
<li><p>Set the <span>drag data store allowed effects state</span>
to the current value of <var title="">dataTransfer</var>'s <code
@@ -94616,15 +94582,12 @@
</dl>
- <p>Otherwise (if the <code
- title="event-dragover">dragover</code> event <em>is</em>
- canceled), set the <span>current drag operation</span> based on
- the values of the <code
- title="dom-DataTransfer-effectAllowed">effectAllowed</code> and
- <code title="dom-DataTransfer-dropEffect">dropEffect</code>
- attributes of the <code>DragEvent</code> object's <code
- title="dom-DragEvent-dataTransfer">dataTransfer</code> object as
- they stood after the event dispatch finished, as per the
+ <p>Otherwise (if the <code title="event-dragover">dragover</code> event <em>is</em> canceled),
+ set the <span>current drag operation</span> based on the values of the <code
+ title="dom-DataTransfer-effectAllowed">effectAllowed</code> and <code
+ title="dom-DataTransfer-dropEffect">dropEffect</code> attributes of the <code>DragEvent</code>
+ object's <code title="dom-DragEvent-dataTransfer">dataTransfer</code> object as they stood
+ after the event <span title="concept-event-dispatch">dispatch</span> finished, as per the
following table:</p>
<table>
@@ -94749,12 +94712,11 @@
<li>
- <p>If the event is canceled, set the <span>current drag
- operation</span> to the value of the <code
- title="dom-DataTransfer-dropEffect">dropEffect</code> attribute
- of the <code>DragEvent</code> object's <code
- title="dom-DragEvent-dataTransfer">dataTransfer</code> object
- as it stood after the event dispatch finished.</p>
+ <p>If the event is canceled, set the <span>current drag operation</span> to the value of the
+ <code title="dom-DataTransfer-dropEffect">dropEffect</code> attribute of the
+ <code>DragEvent</code> object's <code title="dom-DragEvent-dataTransfer">dataTransfer</code>
+ object as it stood after the event <span title="concept-event-dispatch">dispatch</span>
+ finished.</p>
<p>Otherwise, the event is not canceled; perform the event's
default action, which depends on the exact target as
@@ -96639,22 +96601,18 @@
<!--START complete-->
</p>
- <p>For dedicated workers, if the error is still <i
- title="concept-error-nothandled">not handled</i> afterwards, or if
- the error occurred while handling a previous script error, the user
- agent must <span>queue a task</span> to fire an event that uses the
- <code>ErrorEvent</code> interface, with the name <code
- title="event-error">error</code>, that doesn't bubble and is
- cancelable, with its <code
- title="dom-ErrorEvent-message">message</code>, <code
+ <p>For dedicated workers, if the error is still <i title="concept-error-nothandled">not
+ handled</i> afterwards, or if the error occurred while handling a previous script error, the user
+ agent must <span>queue a task</span> to <span title="concept-event-fire">fire</span> a <span
+ title="concept-events-trusted">trusted</span> event that uses the <code>ErrorEvent</code>
+ interface, with the name <code title="event-error">error</code>, that doesn't bubble and is
+ cancelable, with its <code title="dom-ErrorEvent-message">message</code>, <code
title="dom-ErrorEvent-filename">filename</code>, <code
- title="dom-ErrorEvent-lineno">lineno</code>, and <code
- title="dom-ErrorEvent-column">column</code> attributes initialized
- appropriately, at the <code>Worker</code> object associated with the
- worker. If the event is not canceled, the user agent must act as if
- the uncaught runtime script error had occurred in the global scope
- that the <code>Worker</code> object is in, thus repeating the entire
- runtime script error reporting process one level up.</p>
+ title="dom-ErrorEvent-lineno">lineno</code>, and <code title="dom-ErrorEvent-column">column</code>
+ attributes initialized appropriately, at the <code>Worker</code> object associated with the
+ worker. If the event is not canceled, the user agent must act as if the uncaught runtime script
+ error had occurred in the global scope that the <code>Worker</code> object is in, thus repeating
+ the entire runtime script error reporting process one level up.</p>
<p>If the implicit port connecting the worker to its
<code>Worker</code> object has been disentangled (i.e. if the parent
@@ -97093,8 +97051,9 @@
attribute whose value is initialized to a <span title="dfn-read-only-array">read only</span>
array containing only the newly created port, and has a <code
title="dom-MessageEvent-source">source</code> attribute whose value is initialized to the
- newly created port, and <span>queue a task</span> to dispatch the event at <var
- title="">worker global scope</var>.</p></li>
+ newly created port, and <span>queue a task</span> to <span
+ title="concept-event-dispatch">dispatch</span> the event at <var title="">worker global
+ scope</var>.</p></li>
<li>
@@ -97159,8 +97118,9 @@
string, has a <code title="dom-MessageEvent-ports">ports</code> attribute whose value is
initialized to a <span title="dfn-read-only-array">read only</span> array containing only the
newly created port, and has a <code title="dom-MessageEvent-source">source</code> attribute whose
- value is initialized to the newly created port, and <span>queue a task</span> to dispatch the
- event at <var title="">worker global scope</var>.</p></li>
+ value is initialized to the newly created port, and <span>queue a task</span> to <span
+ title="concept-event-dispatch">dispatch</span> the event at <var title="">worker global
+ scope</var>.</p></li>
<li>
@@ -98275,13 +98235,12 @@
title="">event type</var> buffer to the empty string.</p></li>
<li><p><span>Queue a task</span> which, if the <code
- title="dom-EventSource-readyState">readyState</code> attribute is
- set to a value other than <code
- title="dom-EventSource-CLOSED">CLOSED</code>, dispatches the newly
- created event at the <code>EventSource</code> object.</p></li> <!--
- so calling close() drops the messages immediately. The connection
- dying doesn't interfere with already-sent messages since it sets us
- to CLOSED via a task, not synchronously -->
+ title="dom-EventSource-readyState">readyState</code> attribute is set to a value other than <code
+ title="dom-EventSource-CLOSED">CLOSED</code>, <span
+ title="concept-event-dispatch">dispatches</span> the newly created event at the
+ <code>EventSource</code> object.</p></li> <!-- so calling close() drops the messages immediately.
+ The connection dying doesn't interfere with already-sent messages since it sets us to CLOSED via
+ a task, not synchronously -->
</ol>
@@ -99356,7 +99315,7 @@
<li>
- <p>Dispatch <var title="">event</var> at the
+ <p><span title="concept-event-dispatch">Dispatch</span> <var title="">event</var> at the
<code>WebSocket</code> object.</p>
</li>
@@ -99437,8 +99396,8 @@
title="dom-CloseEvent-code">code</code> attribute is initialized to <i>the WebSocket connection
close code</i>, and whose <code title="dom-CloseEvent-reason">reason</code> attribute is
initialized to <i>the WebSocket connection close reason</i> <span>decoded as UTF-8, with error
- handling</span>, and dispatch the event at the <code>WebSocket</code> object. <a
- href="#refsWSP">[WSP]</a></p></li>
+ handling</span>, and <span title="concept-event-dispatch">dispatch</span> the event at the
+ <code>WebSocket</code> object. <a href="#refsWSP">[WSP]</a></p></li>
</ol>
@@ -100081,11 +100040,10 @@
<li>
- <p><span>Queue a task</span> to dispatch the event created in the
- previous step at the <code>Window</code> object on which the
- method was invoked. The <span>task source</span> for this <span
- title="concept-task">task</span> is the <span>posted message task
- source</span>.</p>
+ <p><span>Queue a task</span> to <span title="concept-event-dispatch">dispatch</span> the event
+ created in the previous step at the <code>Window</code> object on which the method was invoked.
+ The <span>task source</span> for this <span title="concept-task">task</span> is the <span>posted
+ message task source</span>.</p>
</li>
@@ -101408,12 +101366,11 @@
storage</a>, <a href="#localStorageEvent">for local
storage</a>).</p>
- <p>When this happens, the user agent must <span>queue a task</span>
- to fire an event with the name <code>storage</code>, which does not
- bubble and is not cancelable, and which uses the
- <code>StorageEvent</code> interface, at each <code>Window</code>
- object whose <code>Document</code> object has a <code>Storage</code>
- object that is affected.</p>
+ <p>When this happens, the user agent must <span>queue a task</span> to <span
+ title="concept-event-fire">fire</span> a <span title="concept-events-trusted">trusted</span> event
+ with the name <code>storage</code>, which does not bubble and is not cancelable, and which uses
+ the <code>StorageEvent</code> interface, at each <code>Window</code> object whose
+ <code>Document</code> object has a <code>Storage</code> object that is affected.</p>
<p class="note">This includes <code>Document</code> objects that are
not <span>fully active</span>, but events fired on those are ignored
@@ -111194,16 +111151,15 @@
<li><p>Set the <code>Document</code>'s <span>page showing</span>
flag to true.</p></li>
- <li><p>Fire a <code title="event-pageshow">pageshow</code> event
- at the <code>Window</code> object of the <code>Document</code>,
- but with its <code title="dom-event-target">target</code> set to
- the <code>Document</code> object (and the <code
- title="dom-event-currentTarget">currentTarget</code> set to the
- <code>Window</code> object), using the
- <code>PageTransitionEvent</code> interface, with the <code
- title="dom-PageTransitionEvent-persisted">persisted</code>
- attribute initialized to false. This event must not bubble, must
- not be cancelable, and has no default action.</p></li>
+ <li><p><span title="concept-event-fire">Fire</span> a <span
+ title="concept-events-trusted">trusted</span> event with the name <code
+ title="event-pageshow">pageshow</code> at the <code>Window</code> object of the
+ <code>Document</code>, but with its <code title="dom-event-target">target</code> set to the
+ <code>Document</code> object (and the <code
+ title="dom-event-currentTarget">currentTarget</code> set to the <code>Window</code> object),
+ using the <code>PageTransitionEvent</code> interface, with the <code
+ title="dom-PageTransitionEvent-persisted">persisted</code> attribute initialized to false. This
+ event must not bubble, must not be cancelable, and has no default action.</p></li>
</ol>
More information about the Commit-Watchers
mailing list