From 3137f5716156a32f98796093ebdeeb75e7db1432 Mon Sep 17 00:00:00 2001 From: Domenic Denicola Date: Thu, 19 May 2016 17:55:18 -0400 Subject: [PATCH] Move scroll position restoration after popstate This fixes #39, given that the majority of browsers now match the popstate, restore position, hashchange order. --- source | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source b/source index 089e5b737c5..914670ef765 100644 --- a/source +++ b/source @@ -82712,10 +82712,6 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O state, but its URL has a fragment, scroll to the fragment.

-

  • If the entry is an entry with persisted user state, the user agent may - restore persisted user state and update - aspects of the document and its rendering.

    • -

  • Let targetRealm be the current Realm Record.

  • If the entry is a state object entry, let state be @@ -82743,6 +82739,10 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O state attribute initialised to the value of state. This event must bubble but not be cancelable and has no default action.

    • +

  • If the entry is an entry with persisted user state, the user agent may + restore persisted user state and update aspects of the document and its + rendering.

    • +

  • If hash changed is true, then fire a trusted event with the name hashchange at the browsing