-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should <a target="_blank">
and window.open
consume the transient activation?
#10108
Comments
This seems like a good idea. Maybe @mustaqahmed can recall why we didn't specify this in the first place. Was it just because it wasn't interoperable, so we weren't sure everyone would be willing to do it? |
Mentioning consumption in the spec makes sense to me.
That matches my understanding: popup blockers came into existence "organically" w/o a spec, and each browser had a slightly different implementation that just worked. I believe another blocker for a possible consensus here is that popup blockers use few other signals (I mean "other than just user activation") like how allowed-sites are handled and the number or the frequency of popup requests. The list of signals used by each browser seems different (as far as I could sense from my 7-yr old experiment). Cataloging all signals used by each browsers could be a good first step if we expect to standardize popup blockers. |
I'll likely start a PR for this soon if that sounds good? |
What is the issue with the HTML Standard?
https://html.spec.whatwg.org/multipage/document-sequences.html#the-rules-for-choosing-a-navigable checks for the transient activation without consuming it. Chromium seems to consume the transient activation in both
<a target="_blank">
andwindow.open
cases per result of test. Gecko only consumes the activation inwindow.open
case. Webkit doesn't consume the activation in either case.The text was updated successfully, but these errors were encountered: