Closed Bug 1445459 Opened 3 years ago Closed 1 year ago
Modify Session Restore to function on the new Child/Parent
In bug 1438272 we are going to be moving Session History to the parent process. This will break a large amount of Session Restore code, as it depends on reading this state from the content process. However, we're actually going to be moving this state into a more useful place (It'll be in the parent process!) and we'll be synchronizing a more complete version of session history (e.g. form field state will be in the parent process), meaning that we can probably simplify Session Restore and avoid the polling overhead in the content process.
mconley - are we starting to track front-end Fission work anywhere yet?
Priority: -- → P2
(In reply to Justin Dolske [:Dolske] from comment #1) > mconley - are we starting to track front-end Fission work anywhere yet? No, not yet. At this point, there's not a whole lot we can do until APIs become exposed to us to transition to. In the meantime, felipe is working on reducing script overhead in content process start-up time as a semi-related project.
Summary: Rework Session Restore for the upcoming changes to Session History → Modify Session Restore to function on the new Child/ParentSHistory APIs
Assignee: nobody → alchen
Status: NEW → ASSIGNED
Type: enhancement → task
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1507287
You need to log in before you can comment on or make changes to this bug.