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
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.
Thank you for proposing Navigation API for inclusion in Interop 2025.
We are pleased to let you know that this proposal was accepted as part of the Navigation API focus area. You can follow the progress of this focus area on the Interop 2025 dashboard.
For an overview of our process, see proposal selection. Thank you for contributing to Interop 2025!
Uh oh!
There was an error while loading. Please reload this page.
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.
The text was updated successfully, but these errors were encountered: