720384 - scroll restoration happens far too late

Status: NEW

(Firefox :: Session Restore, defect)

Description

[Dietrich Ayala (:dietrich)]

i've been meaning to file this bug for ages:

when we restore a page, scroll position is restored far too late in the process.

we'll restore the whole page and reposition scrolling afterwards, which means it occurs while the user can have already started interacting with the page.

i see this sometimes when i undo-close-tab on long or complex pages (i see it on amazon product pages for example).

we should be able to set scroll position much earlier in the process. if there's no api to do so, one should be created in the platform.

Comment 1

[Dietrich Ayala (:dietrich)]

100% reproduceable for me with 'c'.

type 'abc' and immediately the whole string disappears. interestingly, if i start with 'c' it's ok... until another 'c' comes along.

Comment 2

[Dietrich Ayala (:dietrich)]

aaaand the last comment was meant for a completely different bug. ignore.

Comment 3

[Dietrich Ayala (:dietrich)]

marking snappy, since it feels super slow.

Comment 4

[Andres Hernandez [:andreshm]]

I'll take a look at this.

Comment 5

[Andres Hernandez [:andreshm]]

Attachment: Changes

I tried changing the restoreDocument method in SessionRestore.jsm, to restore  all scroll data first, before all the rest of the document data (form data, inner html, styles).  

However, I think we don't have a real gain on this. Even if the 'scrollTo' method is called first, it's still slow. I would say that 'scrollTo' is the one being slow. Any ideas?