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
This was in my navigation transition proposalhttps://github.com/jakearchibald/navigation-transitions/blob/master/README.md …
3 replies 1 retweet 26 likes -
Replying to @jaffathecake @slightlylate and
Very interesting indeed. How do I cancel the navigation to make it into a pushState instead?
3 replies 0 retweets 0 likes -
Replying to @ElliottZ @jaffathecake and
I think what I don't understand about this proposal is it's focused on document swaps, but unless you're going cross origin you want to avoid document swaps at all costs. All Workers die, your framework reloads, CEs are registered again, we must recalculate style the new doc.
1 reply 0 retweets 1 like -
Replying to @ElliottZ @slightlylate and
Few pages have workers. Styles are going to majorly change anyway. Frameworks are *added* to do simple transitions.
1 reply 0 retweets 0 likes -
Replying to @jaffathecake @ElliottZ and
A clear case for this GIF. Transitions are a use case that motivate SPAs, but even multi page apps need pushState for things like lightboxes.
@jaffathecake since portals have momentum, please make sure they cover the same origin transition use case!pic.twitter.com/1VQiZpeGee2 replies 0 retweets 5 likes -
Replying to @cramforce @jaffathecake and
I worry we designed portals wrong for these cases.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @cramforce and1 reply 0 retweets 6 likes
-
Replying to @DasSurma @slightlylate and
In this case it is definitely not too late. Although my superstition is that "putting same origin transition in scope for your web feature is the most certain way to make sure it never ships."
1 reply 0 retweets 2 likes
Think of it as "views". We have a mechanism for views (iframes) this is to heavyweight and disjoint to handle same-origin cases. Portals could be good for this but aren't today AFAICT. How to drive transition from worklet & clobber original document is crux of issue.
-
-
Replying to @slightlylate @DasSurma and
@AliGTheOtherOne's idea was that portals are good for transitions if the portal could have a transparent background color. I think I agree but needs some prototyping. The technology that drives the transition is independent of that.2 replies 0 retweets 1 like -
Replying to @cramforce @DasSurma and
They have to at least be designed to work together as you have to provide a context to drive from so that transitions make visual sense
1 reply 0 retweets 0 likes - 11 more replies
New conversation -
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.