Closed
Bug 698094
Opened 13 years ago
Closed 12 years ago
Remove SessionHistory from the Java process
Categories
(Firefox for Android Graveyard :: General, defect, P4)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mfinkle, Assigned: bnicholson)
Details
The real session history is already stored in gecko. All we seem to need is some flags to say "can we go back" and "can we go forward". We do the same thing in the multi-process XUL UI app. We send the canGoBack and canGoForward booleans in the onLocationChange JSON message and store them in the "Tab". We can do the same thing in Java.
Comment 1•13 years ago
|
||
UX folks were considering behaviour on long-press of the back button that would show the user a list of "back" entries, similar to desktop. This might require storing some session history in Java to implement.
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → bnicholson
Updated•13 years ago
|
Priority: -- → P4
Reporter | ||
Comment 2•12 years ago
|
||
I think the minimum level we store in Java now is enough to support some UX things in the future (do we have a bug filed for the list of back entries?) while not adding additional things like form data, cookies and other stuff that can live nicely in SessionStore.js Closing this for now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•