You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems pretty natural that an entry's view of forward session history will change over time. However, portals/prerendering creates a situation where a the view of backwards session history changes.
While prerendered, the page would (presumably) not have access to previous session history entries of the parent page, but once it activates it will.
Should there be a way to access the previous state while prerendering? Should there be an event when backwards history state changes?
This might be an issue for history built in stages #17.
The text was updated successfully, but these errors were encountered:
domenic
added
the
addition
A proposed addition which could be added later without impacting the rest of the API
label
Feb 25, 2021
I don't think giving prerendered pages insight into their referrer's navigation API history entry list is a good idea. But maybe an event when you start growing entries backward in that way is a good idea.
It seems pretty natural that an entry's view of forward session history will change over time. However, portals/prerendering creates a situation where a the view of backwards session history changes.
While prerendered, the page would (presumably) not have access to previous session history entries of the parent page, but once it activates it will.
Should there be a way to access the previous state while prerendering? Should there be an event when backwards history state changes?
This might be an issue for history built in stages #17.
The text was updated successfully, but these errors were encountered: