-
Notifications
You must be signed in to change notification settings - Fork 698
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
Disowning opener by default for target="_blank"
links
#2799
Comments
Thanks for the heads-up @Malvoz!
Agree and I think we should tie this to the list of target browsers configured by the user. So if any target browser doesn't imply
That seems like a good addition to include too and can probably reported regardless of target browser. |
I opened the same issue for Google's Lighthouse, their stand on warning for links using
Which I think makes sense :) |
New bug for Firefox seems to be https://bugzilla.mozilla.org/show_bug.cgi?id=1522083. Also the feature hasn't landed yet :( |
This issue is about
hint-disown-opener
.Developers have for some time been adviced to set
rel="noopener"
for outgoingtarget="_blank"
links. However, WHATWG spec changes now says these links should implynoopener
by default. That spec change also adds theopener
link relation.I suppose, changes to
hint-disown-opener
should wait until browsers actually implement this. And I think rather than looking fortarget="_blank"
links to includerel="noopener"
- instead perhaps warn if links containrel="opener"
.This is related to potential future checks for the
Cross-Origin-Opener-Policy
HTTP header mentioned in #1633.Additionally, the
rel
attribute is now supported on<form>
elements!The text was updated successfully, but these errors were encountered: