Post

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

easrng 

@easrng.net

Is there a polyfill?

15/1/26, 4:00 pm0 reposts2 likes

easrng 

@easrng.net

15 Jan

ngl I started watching this like 'oh history isn't that bad' but this seems really nice to work with :)

Firefox for Web Developers

@webdevs.firefox.com

15 Jan

I'm not aware of a good quality polyfill. I'm not sure it's possible to build one.

Kevin Crawford

@kcrwfrd.bsky.social

8 Feb

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? 🙏🏼

Firefox for Web Developers

@webdevs.firefox.com

9 Feb

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?

easrng 

@easrng.net

9 Feb

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

Kevin Crawford

@kcrwfrd.bsky.social

9 Feb

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.

Kevin Crawford

@kcrwfrd.bsky.social

8 Feb

Polyfill in question: github.com/kcrwfrd/navi...

github.comGitHub - kcrwfrd/navigation-ponyfill: A ponyfill (polyfill) for the browser Navigation APIA ponyfill (polyfill) for the browser Navigation API - kcrwfrd/navigation-ponyfill

Kevin Crawford

@kcrwfrd.bsky.social

16 Jan

I actually have one that I’ve been working on for the past few weeks, and I would love any feedback on it: github.com/kcrwfrd/navi... I feel quite good about supporting entries(), currentEntry, and canGoBack. I will have to start digging into navigate() @webdevs.firefox.com

github.comGitHub - kcrwfrd/navigation-ponyfill: A ponyfill (polyfill) for the browser Navigation APIA ponyfill (polyfill) for the browser Navigation API - kcrwfrd/navigation-ponyfill

Kevin Crawford

@kcrwfrd.bsky.social

16 Jan

I wouldn’t call it stable yet. It works by patching the history API so that you can use navigation api features in history-based framework routers. I want to make that patching explicitly opt-in so that you could avoid patching altogether and eschew history altogether for a purely navigation router

Kevin Crawford

@kcrwfrd.bsky.social

16 Jan

I have PR open for entries() and currentEntry, I would love any feedback on it ❤️ github.com/kcrwfrd/navi... I need to sort out bundling as well. For now I started out without any bundling just so I can experiment and develop.

github.comfeat: add support for `entries()` and `currentEntry` by kcrwfrd · Pull Request #33 · kcrwfrd/navigation-ponyfillSummary This PR implements the entries() method and currentEntry property from the Navigation API. Key Changes Enhanced and refactored Navigation Added currentEntry getter and entries() method nav...