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.

Sign up for GitHub

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

Jump to bottom

How should force-load-at-top interact with the new Navigation API #242

Open
bokand opened this issue Nov 22, 2023 · 0 comments
Open

How should force-load-at-top interact with the new Navigation API #242

bokand opened this issue Nov 22, 2023 · 0 comments
Labels
spec issue

Comments

@bokand
Copy link
Collaborator

bokand commented Nov 22, 2023

The Navigation API scroll restoration logic doesn't go through the normal Navigation algorithm, instead flowing through the process scroll behavior steps. There's two cases:

  1. The NavigateEvent.scroll() method called by an author
  2. Finishing an intercepted navigation/"transition"

The fix for #186 will fix force-load-at-top for the normal navigation flow but it's not clear to me how it should affect these navigation API paths yet.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
spec issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bokand