-
-
Notifications
You must be signed in to change notification settings - Fork 936
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
Add rel=”noopener” to target="_blank" links to appease CodeQL. #4463
Conversation
CodeQL explicitly says "or" but it's requiring "and".
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4463 +/- ##
=======================================
Coverage 97.13% 97.13%
=======================================
Files 385 385
Lines 8200 8200
=======================================
Hits 7965 7965
Misses 235 235 ☔ View full report in Codecov by Sentry. |
It only trips up on links with |
oh no, I ended up with fancy quotes in here somehow. Very strange. This was the cause of CodeQL not understanding the rel attribute |
6357c86
to
215e908
Compare
215e908
to
195f0bc
Compare
In #4462, CodeQL is making noise about
target="_blank"
links withoutrel="noopener"
. I added it here to quiet CodeQL in future PRs. I doubt that any self respecting client is actually breaking this rule, but might as well.It has also been suggested, and we do this in a few places, to add
noreferrer
as inrel="noopener noreferrer"
. I don't think it's necessary as long as CodeQL is fine with it.For email, I suggest that we remove the target attribute entirely and allow the email client to do its thing.
What do you think? Should we...