Support the Navigation API #11046
loganvolkers
started this conversation in
Proposals
Replies: 3 comments 5 replies
-
Yes, 💯. It is finally possible to get native browser loading indicator showing when navigating between routes in a SPA. This has been long overdue. |
Beta Was this translation helpful? Give feedback.
0 replies
-
We were involved in very early conversations about the navigation API and are happy how it shaped up, all of our feedback seems to have been included. The moment it's practical to use it, we will. |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The Navigation API is a replacement for the History API.
It has graduated from being a HTML Spec PR to a part of the spec and landed in Chrome 110 (~ February 7th 2023, plus other Chromium-based browsers since).
Some excellent features include:
In preliminary results from State of HTML 2023, the Navigation API was a somewhat common response to the freeform question "Which existing HTML features or browser APIs are you unable to use because of browser differences or lack of support?"
Where can I learn more?
Being discussed in the interop project: web-platform-tests/interop#435
What should change in React Router
React Router should rely on the
navigate
event for core state changes. This will make React Router able to operate in an islands architecture of many front-end applications.Beta Was this translation helpful? Give feedback.
All reactions