From d8ee362f28ede478d1f7f316dfb61cf074402ebd Mon Sep 17 00:00:00 2001 From: Anne van Kesteren Date: Thu, 7 Jul 2016 20:55:04 +0200 Subject: [PATCH] Set current entry earlier in "traverse the history" It was inconsistent with pushState() and could actually be observed due to synchronous event dispatch. This also makes a clarifying change to consistently refer to the substeps of a particular step. Fixes #1511. --- source | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source b/source index 9afa388582b..64b14e987df 100644 --- a/source +++ b/source @@ -83088,6 +83088,8 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O URL's fragment is non-null, then scroll to the fragment.

+

  • Set the current entry to entry.

    • +

  • Let targetRealm be the current Realm Record.

  • If entry has a state object, then let state be @@ -83105,9 +83107,9 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O

  • -

    If the non-blocking events flag is not set, then run the following steps - immediately. Otherwise, the non-blocking events flag is set; queue a task - to run the following substeps instead.

    +

    If the non-blocking events flag is not set, then run the following substeps + immediately. Otherwise, the non-blocking events flag is set; queue a + task to run the following substeps instead.

      @@ -83134,8 +83136,6 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O -

    1. Set the current entry to entry.

      2. -

    The task source for the tasks mentioned above is the DOM manipulation task