adding data about implicit rel=noopener behavior#6366
adding data about implicit rel=noopener behavior#6366ddbeck merged 2 commits intomdn:masterfrom chrisdavidmills:implicit-noopener
Conversation
ghost
added
the
data:html
html/elements/a.json
Outdated
| }, | ||
| "implicit_noopener": { | ||
| "__compat": { | ||
| "description": "Setting <code>target=\"_blank\"</code> also provides implicit <code>rel=\"noopener\"</code> behavior", |
There was a problem hiding this comment.
Thank you for this Chris. The data is good. I had a thought that the description could be a bit punchier, like this:
| "description": "Setting <code>target=\"_blank\"</code> also provides implicit <code>rel=\"noopener\"</code> behavior", | |
| "description": "<code>target=\"_blank\"</code> implies <code>rel=\"noopener\"</code> behavior", |
Less wordy still would be this…
| "description": "Setting <code>target=\"_blank\"</code> also provides implicit <code>rel=\"noopener\"</code> behavior", | |
| "description": "<code>target=\"_blank\"</code> implies <code>rel=\"noopener\"</code>", |
…but I'm not sure it's right: someElement.getAttribute("rel") === "noopener" but there's no actual rel="noopener" attribute. I'm not sure if that's a distinction without a difference. I'd be interested in your take.
|
@ddbeck thanks for the advice on wording. I've gone for the first one, as I think being more explicit is useful = it doesn't actually set the attribute, but it implies the behavior. |
|
@chrisdavidmills @ddbeck Starting with version 88, Chrome (and other chromium based browsers) will imply |
3 participants
As per https://bugzilla.mozilla.org/show_bug.cgi?id=1522083
Enabled for Firefox 79.
I got the data for Safari desktop and Chromiums from https://www.fxsitecompat.dev/en-CA/docs/2020/target-blank-on-anchors-now-implies-rel-noopener/