So, internet: can we agree to kill the navigate-to-a-string side-effects of `<a href="javascript:'Hi!'">click</a>`? It's nuts, right?
-
-
Replying to @mikewest
According to https://www.chromestatus.com/metrics/feature/timeline/popularity/215 … we replace the document with the result of `javascript:` on ~2% of page loads! TWO PERCENT. *sobs*
3 replies 3 retweets 16 likes -
Do you include javascript:void(0) in those 2%? That's super common in links with onclick handlers.
1 reply 0 retweets 1 like -
Replying to @johnwilander
: No. This counter only triggers if the result of the `javascript:` execution is a string.
@hillbrad2 replies 0 retweets 0 likes -
-
looks like we do that because... wait for it... about:blank iframes throw mixed content warnings in IE6.
2 replies 0 retweets 5 likes -
-
Replying to @slightlylate
: Well, surely we can point Microsoft folks to the spec and they'll patch that behavior. In IE6. *cough*
@hillbrad2 replies 0 retweets 3 likes
: in fairness, I'm sure a huge % of all the overhead in our Closure-based UIs is down to OldIE workarounds.
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.