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

Navigation API #709

Open
o-t-w opened this issue Sep 17, 2024 · 2 comments
Open

Navigation API #709

o-t-w opened this issue Sep 17, 2024 · 2 comments
Labels
focus-area-proposal Focus Area Proposal

Comments

@o-t-w
Copy link

o-t-w commented Sep 17, 2024 •
edited
Loading

Description

The Navigation API makes it easier for single page apps to handle navigation and updates to the URL. A modern and much improved alternative to the History API.

It cannot be polyfilled, so cross-browser support is crucial.

Specification

https://html.spec.whatwg.org/multipage/nav-history-apis.html#navigation-api

Additional Signals

Supported in Chrome and Edge since version 102.

Positive standards position from Safari and Firefox.

Firefox Bug
Safari Bug

299 likes for this tweet complaining that the Navigation API wasn't included in Interop 2024.

Tweet from a co-creator of React Router, the most popular frontend router.
@o-t-w o-t-w added the focus-area-proposal Focus Area Proposal label Sep 17, 2024
@philwolstenholme
Copy link

For reference:

@gsnedders
Copy link
Member

https://wpt.fyi/results/navigation-api?label=experimental&label=master&aligned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
focus-area-proposal Focus Area Proposal
Projects
Interop 2025
Status: No status
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gsnedders @philwolstenholme @o-t-w