Closed Bug 3891 Opened 21 years ago Closed 21 years ago
[FEATURE] Remember page state in session history
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...)
This is a local history issue.
yeah, i just figured no one got around to implementing this yet. the bug is cross platform, marking as such.
Component: Networking Library → XPApps
OS: Windows NT → All
Priority: P3 → P2
Target Milestone: M7
Set target milestone to M7, changed component to XPApps and priority to P2.
Move this one to M8 ...
Summary: The previous page's Y pos is not restored when doing "back" → [FEATURE]Remember the page's scrollbar position in sessionhistory
Target Milestone: M8 → M9
More things to session History...
This can be fixed only after 9958 is fixed. Moving to M12
Target Milestone: M9 → M12
*** Bug 10008 has been marked as a duplicate of this bug. ***
Summary: [FEATURE]Remember the page's scrollbar position in sessionhistory → [FEATURE] Remember page state in session history
Can this be moved back to M11? Who needs to help to make this happen?
*** Bug 16223 has been marked as a duplicate of this bug. ***
*** Bug 16376 has been marked as a duplicate of this bug. ***
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...
[Resolving priority to level 2] P1 designations are reserved for crash-inducing bugs, yes?
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.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 16806 ***
You need to log in before you can comment on or make changes to this bug.