I really wish the web had a global navigation event I could cancel. So much router logic is just trying to intercept all nav to do pushState.
@DasSurma @bfgeek @slightlylate
-
-
I also loathe the history API. Who was the customer this was designed with? Oy. We discussed such an event a part of the Service Worker design; it has to be scoped to origin, but can work. It'd be something sent before `onbeforeunload`. /cc
@jaffathecake@wanderview4 replies 0 retweets 18 likes -
Replying to @slightlylate @ElliottZ and
I would like to subscribe to your newsletter.
1 reply 0 retweets 8 likes -
Replying to @NellWaliczek @ElliottZ and
I might prototype such an event. Hey
@davidbaron, who's the best Mozilla person to rope into this discussion?2 replies 0 retweets 7 likes -
-
-
Replying to @aerotwist @DasSurma and
Open questions: does this event fire on fragment navigation? Is it still cancellable if dispatched from programmatic parent frame navigation (`iframe.src = ...`)? What is the timing & behaviour relative to window.location synchronous setter?
2 replies 0 retweets 1 like -
Replying to @slightlylate @aerotwist and
Fragment nav: We have onhashchange, but iirc it’s pretty unreliable. Cancellable: I vote yes. App embedding and stuff. Timing: Synchronous after the old APIs, maybe? But I feel like there’s a case to be made for extendable events
2 replies 0 retweets 1 like
Extendable and synchronous are incompatible. You've gotta make the decision *now*.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.