Bug 1654080 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Spoke to Eden and I put my understanding below:

The issue here is that SessionHistory is going to move to the parent process and we need to provide a way for SessionRestore to collect on the parent process.

SessionRestore now collects SessionHistroy data for documents on the content process through a docshell tree. However, when it comes to a cross origin iframe/docshell, SessionRestore cannot find the cross-origin/cross-process SessionHistory data.
Revision 1 by
on 
Spoke to Eden and I put my understanding below:

The issue here is that SessionHistory is going to move to the parent process and we need to provide a way for SessionRestore to collect on the parent process.

SessionRestore now collects SessionStorage data for documents on the content process through a docshell tree. However, when it comes to a cross-origin iframe/docshell, SessionRestore cannot find the cross-origin/cross-process SessionStorage data properly.
Revision 2 by
on 
Spoke to Eden and I put my understanding below:

The issue here is that SessionHistory is going to move to the parent process and we need to provide a way for SessionStore to collect on the parent process.

SessionRestore now collects SessionStorage data for documents on the content process through a docshell tree. However, when it comes to a cross-origin iframe/docshell, SessionRestore cannot find the cross-origin/cross-process SessionStorage data properly.

Back to Bug 1654080 Comment 5