@wanderview hey Ben! Am I missing something here or is this still an issue? Seems like an important one for mobile especially PWAs, etc. https://bugzilla.mozilla.org/show_bug.cgi?id=251784#c10 …
-
-
Replying to @HenrikJoreteg
Sorry, this is outside the small area where I pretend I know something. Maybe
@bz_moz or smaug know the history here.2 replies 0 retweets 2 likes -
Replying to @wanderview @HenrikJoreteg
That page explicitly does document.body.scrollTop = 0, no? The question is whether it does it _before_ or _after_ browsers restore the scroll state. And browsers might differ on that.
2 replies 0 retweets 0 likes -
So for example, <body onload="document.documentElement.scrollTop = 0" onunload="console.log('hey')"> will scroll after restoration in Firefox, but before in Chrome. And I haven't been able to figure out what Chrome's heuristics are here, exactly.
1 reply 0 retweets 1 like
Doing the scroll off a setTimeout(0) from onload, for example, does run after scroll state restoration. So maybe Chrome restores scroll state "after onload" or something. Firefox restores as we load, so for a long doc you can restore and start reading before it's all parsed.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.