From cf02423dc52686d084a3191833d939919b5907fd Mon Sep 17 00:00:00 2001
From: Anne van Kesteren
Cancel any preexisting but not yet mature
attempt to navigate browsingContext, including canceling any instances of the 1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
When a user agent is supposed to navigate to a fragment, then the user agent must
- run the following steps: When a user agent is supposed to navigate to a fragment, optionally with replacement enabled,
+ then the user agent must run the following steps: Remove all the entries in the browsing context's session history
- after the current entry. If the current entry is the last entry in the
- session history, then no entries are removed. If not with replacement enabled, then remove all the entries in the
+ browsing context's session history after the current
+ entry. If the current entry is the last entry in the session history, then
+ no entries are removed. This doesn't necessarily have to affect the user
agent's user interface. Remove any tasks queued by the history traversal
@@ -82811,10 +82811,10 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
the user agent was navigating. The title must be left
unset. Traverse the history to the new entry, with the non-blocking events flag
- set. This will scroll to the fragment given in what is now the document's URL. Traverse the history to the new entry, with replacement enabled
+ if this was invoked with replacement enabled, and with the non-blocking
+ events flag set. This will scroll to the fragment given in what is now the
+ document's URL. If the scrolling fails because the relevant ID has
@@ -120555,6 +120555,7 @@ INSERT INTERFACES HERE
Felix Sanz,
Felix Sasaki,
Fernando Altomare Serboncini,
+ Forbes Lindesay,
Francesco Schwarz,
Francis Brosnan Blazquez,
Franck 'Shift' Quélain,
Navigating to a fragment
-
-