Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interaction with portals/prerendering #45

Open
jakearchibald opened this issue Feb 24, 2021 · 1 comment
Open

Interaction with portals/prerendering #45

jakearchibald opened this issue Feb 24, 2021 · 1 comment
Labels
addition A proposed addition which could be added later without impacting the rest of the API

Comments

@jakearchibald
Copy link

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.

@domenic domenic added the addition A proposed addition which could be added later without impacting the rest of the API label Feb 25, 2021
@domenic
Copy link
Collaborator

domenic commented May 27, 2021

This was discussed a bit in https://bugs.chromium.org/p/chromium/issues/detail?id=1212819. Note that history will only extend backward if we resolve #71 by doing no-BCG-scoping. (Which I think is correct.)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addition A proposed addition which could be added later without impacting the rest of the API
Projects
None yet
Development

No branches or pull requests

2 participants