feat(no-target-blank): Configure noreferrer requirement #2478
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ljharb
approved these changes
Nov 29, 2019
ljharb
force-pushed
the
feat/no-target-blank/explicit-referrer
branch
from
ef4ef2a
to
d3b5d71
Compare
This was referenced Dec 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows
<a href="foobar" target="_blank" rel="noopener"></a>if the rule is configured withallowReferrerfor links where we want thereferrerfor tracking. For rationale see #2054 (comment).referreris not a specified link type so I'd rather not introduce this magic-word for this rule.See #776 (can be closed with this change?) and #2054