Closed
Bug 983457
Opened 11 years ago
Closed 9 years ago
Preserve history stack for when Marketplace is preemptively killed
Categories
(Marketplace Graveyard :: Consumer Pages, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: cvan, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [repoman][marketplace-transition])
As a single-page app, we use `window.history.pushState` to push new pages onto the history stack.
When a user leaves the Marketplace (to play a game he just installed, for example) the Marketplace is no longer in focus and usually because of memory limitations on the Firefox OS devices, the Marketplace's background process gets killed.
When the user relaunches the Marketplace, his history is gone, and he has to find the last page he was on.
Let's persist the history stack (for a reasonable amount of time - say, an hour) in localStorage/IndexedDB, so that when a user relaunches the Marketplace (*as an app*) we remember the last page the user was viewing (and all the previous pages they were viewing). The history stack is small, and this is pretty trivial.
Updated•11 years ago
|
Blocks: tarako-marketplace
Updated•11 years ago
|
No longer blocks: tarako-marketplace
Updated•10 years ago
|
Whiteboard: [repoman]
Updated•10 years ago
|
Blocks: marketplace-perf
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Whiteboard: [repoman] → [repoman][marketplace-transition]
You need to log in
before you can comment on or make changes to this bug.
Description
•