[html5] r7372 - [e] (0) Fix the use of 'must' in this algorithm, which was inconsistent. This ch [...]

whatwg at whatwg.org whatwg at whatwg.org
Tue Sep 18 15:09:56 PDT 2012


Author: ianh
Date: 2012-09-18 15:09:55 -0700 (Tue, 18 Sep 2012)
New Revision: 7372

Modified:
   complete.html
   index
   source
Log:
[e] (0) Fix the use of 'must' in this algorithm, which was inconsistent. This change should have no normative side-effects.
Affected topics: HTML

Modified: complete.html
===================================================================
--- complete.html	2012-09-18 22:02:32 UTC (rev 7371)
+++ complete.html	2012-09-18 22:09:55 UTC (rev 7372)
@@ -71475,17 +71475,16 @@
   the new page</a>.</p>
 
   <ol><li><p>If there is no longer a <code><a href=#document>Document</a></code> object for the
-   entry in question, the user agent must
-   <a href=#navigate>navigate</a><!--DONAV history traversal after eviction-->
-   the browsing context to the location for that entry to perform an
-   <a href=#entry-update>entry update</a> of that entry, and abort these steps. The
-   "<a href=#navigate>navigate</a>" algorithm reinvokes this "traverse"
-   algorithm to complete the traversal, at which point there
-   <em>is</em> a <code><a href=#document>Document</a></code> object and so this step gets
-   skipped. The navigation must be done using the same <a href=#source-browsing-context>source
-   browsing context</a> as was used the first time this entry was
-   created. (This can never happen with <a href=#replacement-enabled>replacement
-   enabled</a>.)</li>
+   entry in question, <a href=#navigate>navigate</a><!--DONAV history traversal
+   after eviction--> the browsing context to the location for that
+   entry to perform an <a href=#entry-update>entry update</a> of that entry, and
+   abort these steps. The "<a href=#navigate>navigate</a>" algorithm reinvokes
+   this "traverse" algorithm to complete the traversal, at which point
+   there <em>is</em> a <code><a href=#document>Document</a></code> object and so this step
+   gets skipped. The navigation must be done using the same
+   <a href=#source-browsing-context>source browsing context</a> as was used the first time
+   this entry was created. (This can never happen with
+   <a href=#replacement-enabled>replacement enabled</a>.)</li>
 
    <li><p>If the <a href=#current-entry>current entry</a>'s title was not set by the
    <code title=dom-history-pushState><a href=#dom-history-pushstate>pushState()</a></code> or <code title=dom-history-replaceState><a href=#dom-history-replacestate>replaceState()</a></code> methods,
@@ -71500,45 +71499,51 @@
 
    <li><p>If the <var title="">specified entry</var> has a different
    <code><a href=#document>Document</a></code> object than the <a href=#current-entry>current entry</a>
-   then the user agent must run the following substeps:</p>
+   then the following substeps:</p>
 
-    <ol><li>If the browsing context is a <a href=#top-level-browsing-context>top-level browsing
-     context</a>, but not an <a href=#auxiliary-browsing-context>auxiliary browsing
-     context</a>, and the <a href=#origin>origin</a> of the
-     <code><a href=#document>Document</a></code> of the <var title="">specified entry</var>
-     is not the <a href=#same-origin title="same origin">same</a> as the
-     <a href=#origin>origin</a> of the <code><a href=#document>Document</a></code> of the
-     <a href=#current-entry>current entry</a>, then the following sub-sub-steps must
-     be run:
+    <ol><li>
 
-      <ol><li>The current <a href=#browsing-context-name>browsing context name</a> must be
+      <p>If the browsing context is a <a href=#top-level-browsing-context>top-level browsing
+      context</a>, but not an <a href=#auxiliary-browsing-context>auxiliary browsing
+      context</a>, and the <a href=#origin>origin</a> of the
+      <code><a href=#document>Document</a></code> of the <var title="">specified entry</var>
+      is not the <a href=#same-origin title="same origin">same</a> as the
+      <a href=#origin>origin</a> of the <code><a href=#document>Document</a></code> of the
+      <a href=#current-entry>current entry</a>, then run the following
+      sub-sub-steps:</p>
+
+      <ol><li><p>The current <a href=#browsing-context-name>browsing context name</a> must be
        stored with all the entries in the history that are associated
        with <code><a href=#document>Document</a></code> objects with the <a href=#same-origin>same
        origin</a> as the <a href=#active-document>active document</a> <em>and</em>
        that are contiguous with the <a href=#current-entry>current entry</a>.</li>
 
-       <li id=resetBCName>The browsing context's <a href=#browsing-context-name>browsing
+       <li id=resetBCName><p>The browsing context's <a href=#browsing-context-name>browsing
        context name</a> must be unset.</li>
 
       </ol></li>
 
-     <li id=appcache-history-2>The user agent must make the <var title="">specified entry</var>'s <code><a href=#document>Document</a></code> object the
-     <a href=#active-document>active document</a> of the <a href=#browsing-context>browsing
-     context</a>.</li>
+     <li id=appcache-history-2><p>Make the <var title="">specified
+     entry</var>'s <code><a href=#document>Document</a></code> object the <a href=#active-document>active
+     document</a> of the <a href=#browsing-context>browsing context</a>.</li>
 
-     <li>If the <var title="">specified entry</var> has a <a href=#browsing-context-name>browsing
-     context name</a> stored with it, then the following
-     sub-sub-steps must be run:
+     <li>
 
-      <ol><li>The browsing context's <a href=#browsing-context-name>browsing context name</a>
-       must be set to the name stored with the specified entry.</li>
+      <p>If the <var title="">specified entry</var> has a
+      <a href=#browsing-context-name>browsing context name</a> stored with it, then run the
+      following sub-sub-steps:</p>
 
-       <li>Any <a href=#browsing-context-name>browsing context name</a> stored with the
-       entries in the history that are associated with
-       <code><a href=#document>Document</a></code> objects with the <a href=#same-origin>same origin</a>
-       as the new <a href=#active-document>active document</a>, and that are
-       contiguous with the specified entry, must be cleared.</li>
+      <ol><li><p>Set the browsing context's <a href=#browsing-context-name>browsing context
+       name</a> to the name stored with the specified
+       entry.</li>
 
+       <li><p>Clear any <a href=#browsing-context-name title="browsing context name">browsing
+       context names</a> stored with all entries in the history
+       that are associated with <code><a href=#document>Document</a></code> objects with the
+       <a href=#same-origin>same origin</a> as the new <a href=#active-document>active
+       document</a> and that are contiguous with the specified
+       entry.</li>
+
       </ol></li>
 
      <li id=history-autocomplete><p>If the <var title="">specified
@@ -71546,22 +71551,26 @@
      <a href=#autofill-field-name>autofill field name</a> is "<code title=attr-fe-autocomplete-off><a href=#attr-fe-autocomplete-off>off</a></code>", invoke the <a href=#concept-form-reset-control title=concept-form-reset-control>reset algorithm</a> of each
      of those elements.</li>
 
-     <li><p>If the <a href=#current-document-readiness>current document readiness</a> of the <var title="">specified entry</var>'s <code><a href=#document>Document</a></code> is
-     "<code title="">complete</code>", <a href=#queue-a-task>queue a task</a> to 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 <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>
 
-     <!-- an interesting thing to test would be to traverse back
-     during onload, before the first pageshow has fired, and then to
-     traverse forward again, and see if we get _two_ pageshows. If so,
-     it indicates that the history traversal task source has a higher
-     priority than the DOM manipulation task source. -->
+      <p>If the <a href=#current-document-readiness>current document readiness</a> of the <var title="">specified entry</var>'s <code><a href=#document>Document</a></code> is "<code title="">complete</code>", <a href=#queue-a-task>queue a task</a> to run the
+      following sub-sub-steps:</p>
 
+      <ol><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
+       <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>
+
+      </ol><!-- an interesting thing to test would be to traverse back
+      during onload, before the first pageshow has fired, and then to
+      traverse forward again, and see if we get _two_ pageshows. If
+      so, it indicates that the history traversal task source has a
+      higher priority than the DOM manipulation task source. --></li>
+
     </ol></li>
 
    <li><p>Set <a href="#the-document's-address">the document's address</a> to the URL of the
@@ -71631,8 +71640,7 @@
    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>
+   <li><p>The <a href=#current-entry>current entry</a> is now the <var title="">specified entry</var>.</li>
 
   </ol><p>The <a href=#task-source>task source</a> for the tasks mentioned above is the
   <a href=#dom-manipulation-task-source>DOM manipulation task source</a>.</p>

Modified: index
===================================================================
--- index	2012-09-18 22:02:32 UTC (rev 7371)
+++ index	2012-09-18 22:09:55 UTC (rev 7372)
@@ -71475,17 +71475,16 @@
   the new page</a>.</p>
 
   <ol><li><p>If there is no longer a <code><a href=#document>Document</a></code> object for the
-   entry in question, the user agent must
-   <a href=#navigate>navigate</a><!--DONAV history traversal after eviction-->
-   the browsing context to the location for that entry to perform an
-   <a href=#entry-update>entry update</a> of that entry, and abort these steps. The
-   "<a href=#navigate>navigate</a>" algorithm reinvokes this "traverse"
-   algorithm to complete the traversal, at which point there
-   <em>is</em> a <code><a href=#document>Document</a></code> object and so this step gets
-   skipped. The navigation must be done using the same <a href=#source-browsing-context>source
-   browsing context</a> as was used the first time this entry was
-   created. (This can never happen with <a href=#replacement-enabled>replacement
-   enabled</a>.)</li>
+   entry in question, <a href=#navigate>navigate</a><!--DONAV history traversal
+   after eviction--> the browsing context to the location for that
+   entry to perform an <a href=#entry-update>entry update</a> of that entry, and
+   abort these steps. The "<a href=#navigate>navigate</a>" algorithm reinvokes
+   this "traverse" algorithm to complete the traversal, at which point
+   there <em>is</em> a <code><a href=#document>Document</a></code> object and so this step
+   gets skipped. The navigation must be done using the same
+   <a href=#source-browsing-context>source browsing context</a> as was used the first time
+   this entry was created. (This can never happen with
+   <a href=#replacement-enabled>replacement enabled</a>.)</li>
 
    <li><p>If the <a href=#current-entry>current entry</a>'s title was not set by the
    <code title=dom-history-pushState><a href=#dom-history-pushstate>pushState()</a></code> or <code title=dom-history-replaceState><a href=#dom-history-replacestate>replaceState()</a></code> methods,
@@ -71500,45 +71499,51 @@
 
    <li><p>If the <var title="">specified entry</var> has a different
    <code><a href=#document>Document</a></code> object than the <a href=#current-entry>current entry</a>
-   then the user agent must run the following substeps:</p>
+   then the following substeps:</p>
 
-    <ol><li>If the browsing context is a <a href=#top-level-browsing-context>top-level browsing
-     context</a>, but not an <a href=#auxiliary-browsing-context>auxiliary browsing
-     context</a>, and the <a href=#origin>origin</a> of the
-     <code><a href=#document>Document</a></code> of the <var title="">specified entry</var>
-     is not the <a href=#same-origin title="same origin">same</a> as the
-     <a href=#origin>origin</a> of the <code><a href=#document>Document</a></code> of the
-     <a href=#current-entry>current entry</a>, then the following sub-sub-steps must
-     be run:
+    <ol><li>
 
-      <ol><li>The current <a href=#browsing-context-name>browsing context name</a> must be
+      <p>If the browsing context is a <a href=#top-level-browsing-context>top-level browsing
+      context</a>, but not an <a href=#auxiliary-browsing-context>auxiliary browsing
+      context</a>, and the <a href=#origin>origin</a> of the
+      <code><a href=#document>Document</a></code> of the <var title="">specified entry</var>
+      is not the <a href=#same-origin title="same origin">same</a> as the
+      <a href=#origin>origin</a> of the <code><a href=#document>Document</a></code> of the
+      <a href=#current-entry>current entry</a>, then run the following
+      sub-sub-steps:</p>
+
+      <ol><li><p>The current <a href=#browsing-context-name>browsing context name</a> must be
        stored with all the entries in the history that are associated
        with <code><a href=#document>Document</a></code> objects with the <a href=#same-origin>same
        origin</a> as the <a href=#active-document>active document</a> <em>and</em>
        that are contiguous with the <a href=#current-entry>current entry</a>.</li>
 
-       <li id=resetBCName>The browsing context's <a href=#browsing-context-name>browsing
+       <li id=resetBCName><p>The browsing context's <a href=#browsing-context-name>browsing
        context name</a> must be unset.</li>
 
       </ol></li>
 
-     <li id=appcache-history-2>The user agent must make the <var title="">specified entry</var>'s <code><a href=#document>Document</a></code> object the
-     <a href=#active-document>active document</a> of the <a href=#browsing-context>browsing
-     context</a>.</li>
+     <li id=appcache-history-2><p>Make the <var title="">specified
+     entry</var>'s <code><a href=#document>Document</a></code> object the <a href=#active-document>active
+     document</a> of the <a href=#browsing-context>browsing context</a>.</li>
 
-     <li>If the <var title="">specified entry</var> has a <a href=#browsing-context-name>browsing
-     context name</a> stored with it, then the following
-     sub-sub-steps must be run:
+     <li>
 
-      <ol><li>The browsing context's <a href=#browsing-context-name>browsing context name</a>
-       must be set to the name stored with the specified entry.</li>
+      <p>If the <var title="">specified entry</var> has a
+      <a href=#browsing-context-name>browsing context name</a> stored with it, then run the
+      following sub-sub-steps:</p>
 
-       <li>Any <a href=#browsing-context-name>browsing context name</a> stored with the
-       entries in the history that are associated with
-       <code><a href=#document>Document</a></code> objects with the <a href=#same-origin>same origin</a>
-       as the new <a href=#active-document>active document</a>, and that are
-       contiguous with the specified entry, must be cleared.</li>
+      <ol><li><p>Set the browsing context's <a href=#browsing-context-name>browsing context
+       name</a> to the name stored with the specified
+       entry.</li>
 
+       <li><p>Clear any <a href=#browsing-context-name title="browsing context name">browsing
+       context names</a> stored with all entries in the history
+       that are associated with <code><a href=#document>Document</a></code> objects with the
+       <a href=#same-origin>same origin</a> as the new <a href=#active-document>active
+       document</a> and that are contiguous with the specified
+       entry.</li>
+
       </ol></li>
 
      <li id=history-autocomplete><p>If the <var title="">specified
@@ -71546,22 +71551,26 @@
      <a href=#autofill-field-name>autofill field name</a> is "<code title=attr-fe-autocomplete-off><a href=#attr-fe-autocomplete-off>off</a></code>", invoke the <a href=#concept-form-reset-control title=concept-form-reset-control>reset algorithm</a> of each
      of those elements.</li>
 
-     <li><p>If the <a href=#current-document-readiness>current document readiness</a> of the <var title="">specified entry</var>'s <code><a href=#document>Document</a></code> is
-     "<code title="">complete</code>", <a href=#queue-a-task>queue a task</a> to 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 <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>
 
-     <!-- an interesting thing to test would be to traverse back
-     during onload, before the first pageshow has fired, and then to
-     traverse forward again, and see if we get _two_ pageshows. If so,
-     it indicates that the history traversal task source has a higher
-     priority than the DOM manipulation task source. -->
+      <p>If the <a href=#current-document-readiness>current document readiness</a> of the <var title="">specified entry</var>'s <code><a href=#document>Document</a></code> is "<code title="">complete</code>", <a href=#queue-a-task>queue a task</a> to run the
+      following sub-sub-steps:</p>
 
+      <ol><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
+       <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>
+
+      </ol><!-- an interesting thing to test would be to traverse back
+      during onload, before the first pageshow has fired, and then to
+      traverse forward again, and see if we get _two_ pageshows. If
+      so, it indicates that the history traversal task source has a
+      higher priority than the DOM manipulation task source. --></li>
+
     </ol></li>
 
    <li><p>Set <a href="#the-document's-address">the document's address</a> to the URL of the
@@ -71631,8 +71640,7 @@
    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>
+   <li><p>The <a href=#current-entry>current entry</a> is now the <var title="">specified entry</var>.</li>
 
   </ol><p>The <a href=#task-source>task source</a> for the tasks mentioned above is the
   <a href=#dom-manipulation-task-source>DOM manipulation task source</a>.</p>

Modified: source
===================================================================
--- source	2012-09-18 22:02:32 UTC (rev 7371)
+++ source	2012-09-18 22:09:55 UTC (rev 7372)
@@ -83534,17 +83534,16 @@
   <ol>
 
    <li><p>If there is no longer a <code>Document</code> object for the
-   entry in question, the user agent must
-   <span>navigate</span><!--DONAV history traversal after eviction-->
-   the browsing context to the location for that entry to perform an
-   <span>entry update</span> of that entry, and abort these steps. The
-   "<span>navigate</span>" algorithm reinvokes this "traverse"
-   algorithm to complete the traversal, at which point there
-   <em>is</em> a <code>Document</code> object and so this step gets
-   skipped. The navigation must be done using the same <span>source
-   browsing context</span> as was used the first time this entry was
-   created. (This can never happen with <span>replacement
-   enabled</span>.)</p></li>
+   entry in question, <span>navigate</span><!--DONAV history traversal
+   after eviction--> the browsing context to the location for that
+   entry to perform an <span>entry update</span> of that entry, and
+   abort these steps. The "<span>navigate</span>" algorithm reinvokes
+   this "traverse" algorithm to complete the traversal, at which point
+   there <em>is</em> a <code>Document</code> object and so this step
+   gets skipped. The navigation must be done using the same
+   <span>source browsing context</span> as was used the first time
+   this entry was created. (This can never happen with
+   <span>replacement enabled</span>.)</p></li>
 
    <li><p>If the <span>current entry</span>'s title was not set by the
    <code title="dom-history-pushState">pushState()</code> or <code
@@ -83561,53 +83560,58 @@
 
    <li><p>If the <var title="">specified entry</var> has a different
    <code>Document</code> object than the <span>current entry</span>
-   then the user agent must run the following substeps:</p>
+   then the following substeps:</p>
 
     <ol>
 
-     <li>If the browsing context is a <span>top-level browsing
-     context</span>, but not an <span>auxiliary browsing
-     context</span>, and the <span>origin</span> of the
-     <code>Document</code> of the <var title="">specified entry</var>
-     is not the <span title="same origin">same</span> as the
-     <span>origin</span> of the <code>Document</code> of the
-     <span>current entry</span>, then the following sub-sub-steps must
-     be run:
+     <li>
 
+      <p>If the browsing context is a <span>top-level browsing
+      context</span>, but not an <span>auxiliary browsing
+      context</span>, and the <span>origin</span> of the
+      <code>Document</code> of the <var title="">specified entry</var>
+      is not the <span title="same origin">same</span> as the
+      <span>origin</span> of the <code>Document</code> of the
+      <span>current entry</span>, then run the following
+      sub-sub-steps:</p>
+
       <ol>
 
-       <li>The current <span>browsing context name</span> must be
+       <li><p>The current <span>browsing context name</span> must be
        stored with all the entries in the history that are associated
        with <code>Document</code> objects with the <span>same
        origin</span> as the <span>active document</span> <em>and</em>
-       that are contiguous with the <span>current entry</span>.</li>
+       that are contiguous with the <span>current entry</span>.</p></li>
 
-       <li id="resetBCName">The browsing context's <span>browsing
-       context name</span> must be unset.</li>
+       <li id="resetBCName"><p>The browsing context's <span>browsing
+       context name</span> must be unset.</p></li>
 
       </ol>
 
      </li>
 
-     <li id="appcache-history-2">The user agent must make the <var
-     title="">specified entry</var>'s <code>Document</code> object the
-     <span>active document</span> of the <span>browsing
-     context</span>.</li>
+     <li id="appcache-history-2"><p>Make the <var title="">specified
+     entry</var>'s <code>Document</code> object the <span>active
+     document</span> of the <span>browsing context</span>.</p></li>
 
-     <li>If the <var title="">specified entry</var> has a <span>browsing
-     context name</span> stored with it, then the following
-     sub-sub-steps must be run:
+     <li>
 
+      <p>If the <var title="">specified entry</var> has a
+      <span>browsing context name</span> stored with it, then run the
+      following sub-sub-steps:</p>
+
       <ol>
 
-       <li>The browsing context's <span>browsing context name</span>
-       must be set to the name stored with the specified entry.</li>
+       <li><p>Set the browsing context's <span>browsing context
+       name</span> to the name stored with the specified
+       entry.</p></li>
 
-       <li>Any <span>browsing context name</span> stored with the
-       entries in the history that are associated with
-       <code>Document</code> objects with the <span>same origin</span>
-       as the new <span>active document</span>, and that are
-       contiguous with the specified entry, must be cleared.</li>
+       <li><p>Clear any <span title="browsing context name">browsing
+       context names</span> stored with all entries in the history
+       that are associated with <code>Document</code> objects with the
+       <span>same origin</span> as the new <span>active
+       document</span> and that are contiguous with the specified
+       entry.</p></li>
 
       </ol>
 
@@ -83620,26 +83624,37 @@
      title="concept-form-reset-control">reset algorithm</span> of each
      of those elements.</p></li>
 
-     <li><p>If the <span>current document readiness</span> of the <var
-     title="">specified entry</var>'s <code>Document</code> is
-     "<code title="">complete</code>", <span>queue a task</span> to 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
-     <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>
 
-     <!-- an interesting thing to test would be to traverse back
-     during onload, before the first pageshow has fired, and then to
-     traverse forward again, and see if we get _two_ pageshows. If so,
-     it indicates that the history traversal task source has a higher
-     priority than the DOM manipulation task source. -->
+      <p>If the <span>current document readiness</span> of the <var
+      title="">specified entry</var>'s <code>Document</code> is "<code
+      title="">complete</code>", <span>queue a task</span> to run the
+      following sub-sub-steps:</p>
 
+      <ol>
+
+       <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
+       <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>
+
+      </ol>
+
+      <!-- an interesting thing to test would be to traverse back
+      during onload, before the first pageshow has fired, and then to
+      traverse forward again, and see if we get _two_ pageshows. If
+      so, it indicates that the history traversal task source has a
+      higher priority than the DOM manipulation task source. -->
+
+     </li>
+
     </ol>
 
    </li>
@@ -83723,8 +83738,8 @@
    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>
+   <li><p>The <span>current entry</span> is now the <var
+   title="">specified entry</var>.</p></li>
 
   </ol>
 




More information about the Commit-Watchers mailing list