You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Developers have for some time been adviced to set rel="noopener" for outgoing target="_blank" links. However, WHATWG spec changes now says these links should imply noopener by default. That spec change also adds the opener link relation.
I suppose, changes to hint-disown-opener should wait until browsers actually implement this. And I think rather than looking for target="_blank" links to include rel="noopener" - instead perhaps warn if links contain rel="opener".
This is related to potential future checks for the Cross-Origin-Opener-Policy HTTP header mentioned in #1633.
I suppose, changes to hint-disown-opener should wait until browsers actually implement this.
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 noopener by default webhint would give the current advice. If all target browsers imply noopener by default then webhint would even advise removing it as it would be unnecessary.
instead perhaps warn if links contain rel="opener"
That seems like a good addition to include too and can probably reported regardless of target browser.
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: