3891 - [FEATURE] Remember page state in session history

Status: VERIFIED DUPLICATE of bug 16806

(SeaMonkey :: UI Design, defect, P1)

Description

[Roland Mainz]

THe previous page's Y position is not restored when clicking on the
"Back"-Button.

Example: Go to http://www.scripting.com, move into the middle of the page,
click/visit a link, then go "Back". You'll end at the top of www.scripting.com,
not in the middle.

Other note:
Be !! sure !! that the cache does mark incomplete loaded documents/files, and
that error codes like 4xx (405 etc) are not cached (as documents... the server
may return a description as HTML file, but it may not be the requested one...)

Comment 1

[karnaze (gone)]

This is a local history issue.

Comment 2

[Claudius Gayle]

yeah, i just figured no one got around to implementing this yet. the bug is cross platform, marking as such.

Comment 3

[don]

Set target milestone to M7, changed component to XPApps and priority to P2.

Comment 4

[don]

Move this one to M8 ...

Comment 5

[Radha on family leave (not reading bugmail)]

More things to session History...

Comment 6

[Radha on family leave (not reading bugmail)]

This can be fixed only after 9958 is fixed. Moving to M12

Comment 7

[Radha on family leave (not reading bugmail)]

*** Bug 10008 has been marked as a duplicate of this bug. ***

Comment 8

[don]

Can this be moved back to M11?  Who needs to help to make this happen?

Comment 9

[Mats Palmgren (inactive)]

*** Bug 16223 has been marked as a duplicate of this bug. ***

Comment 10

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

*** Bug 16376 has been marked as a duplicate of this bug. ***

Comment 11

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I filed bug 16376 when I was unable to find this one.  A few important comments
from that bug:

One tricky issue with this bug is named anchors:  you want to preserve the
position *separately* for each named anchor.  (This is unlike form controls (see
bug 16379), where I think you want to hold the data even when the named anchor
changes.)

This should be tested carefully with frames, too...

Comment 12

[Crysgem]

[Resolving priority to level 2]
P1 designations are reserved for crash-inducing bugs, yes?

Comment 13

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Setting priority back to P1.  The priority field is used by the bug owner to
prioritize work.  I know that Kipp prefers to use P1 only for crashers, but that
doesn't mean everyone does.

Comment 14

[Radha on family leave (not reading bugmail)]

*** This bug has been marked as a duplicate of 16806 ***

Comment 15

[Claudius Gayle]

VERIFIED dupe.