Post

The Navigation API is newly baseline! The web now has sensible, low-level routing for navigations.

Is there a polyfill?

I released a polyfill with pretty good good support for navigation history entries. As I start to think about how to tackle navigation transition lifecycle (Navigate event, cancellation, interceptors, etc.) I was wondering if you have any wisdom to share in the parts you think are impossible? 🙏🏼

Keeping the browser loading spinner going pops to mind, but there may be more. Things like knowing a navigation is just a `hashChange` seems tricky in the case of traversals. As in, how do you know it's same-document or not?

>Keeping the browser loading spinner going I think this could be done with serviceworkers/iframes maybe?

Yeah, hash changes were tricky to handle, but I think I got it down. I was surprised to learn they fire a popstate event! All of my e2e tests around history entries work with both native Navigation or the polyfill so far.