Probably @bz_moz or someone he delegates to.
-
-
Replying to @davidbaron @slightlylate and
smaug might also be good for this. In general, sending an event when navigation starts to the same origin as the currently loaded origin doesn't seem like a problem to me. There are issues to sort out wrt named targeting and whatnot, reentrancy, etc, etc.
1 reply 0 retweets 0 likes -
Replying to @really_bz @bz_moz and
Would sending an event for cross origin navigations be a problem?
1 reply 0 retweets 0 likes -
Replying to @jaffathecake @davidbaron and
There are issues. Certainly for cross-origin navigations using the browser UI you would not want to expose the URL in the event (something that I expect people want for the pushState use case described above) and you would not want to allow canceling either.
2 replies 0 retweets 1 like -
Replying to @really_bz @bz_moz and
The idea is cross-origin navigation would never trigger the event. Strictly same-origin.
2 replies 0 retweets 0 likes -
-
Replying to @jaffathecake @slightlylate and
I think cross origin would be fine if the navigation was initiated by the document itself. You can already capture those by listening on clicks to cross origin links.
1 reply 0 retweets 3 likes -
Replying to @ElliottZ @slightlylate and
Agreed. The event should fire for navigations initiated by the client & targets the same client. A target=_blank link: nope. A cmd-clicked link: nope. User types in the address bar: nope. User regular-clicks a link without a target: yep.
2 replies 0 retweets 7 likes -
Replying to @jaffathecake @ElliottZ and
How about "user edits the address bar to a same-origin url"? Think changing the tweet id on twitter. What are the exact use cases this is trying to address? Just capturing link clicks is not too hard, but it sounds like people have complicated logic to capture ... what?
1 reply 0 retweets 1 like -
Replying to @really_bz @bz_moz and
I don't think it should fire the event if the user edits the address bar. Monitoring all page-triggered navigations is hard, especially if some are the result of setting location.href, some are history.back etc etc.
3 replies 0 retweets 1 like
If history.back is involved, you can have pretty nonlocal effects (i.e. call is in one subframe but the navigation happens in a totally different subframe). Needs some though there. Also need some thought about script in page A setting .location on page B and whatnot.
-
-
Replying to @really_bz @bz_moz and
I'm trying to understand which of these cases one has to handle to replace current router practice. If they plug directly into popstate events, that clarifies.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.