Uh oh!
There was an error while loading. Please reload this page.
Fix #914 - #917
Conversation
anikethsaha
commented
Dec 2, 2019
the motive is to stop opening new tabs right ? Anything extra this is doing ? |
vkallore
commented
Dec 2, 2019
Its not to prevent opening in new tab. Read about the risk of not adding it here |
anikethsaha
commented
Dec 2, 2019
ahh...make sense. What is the behavior of this PR when externallinktarget is |
vkallore
commented
Dec 2, 2019
As you can see in this PR commit #4769018, if the dev forgot to add the Does it make sense? |
anikethsaha
commented
Dec 2, 2019
I read the description already. What I was asking is whats the behavior of having both |
vkallore
commented
Dec 2, 2019
Well, its required only for |
anikethsaha
commented
Dec 2, 2019
SO if |
vkallore
commented
Dec 2, 2019
|
anikethsaha
commented
Dec 2, 2019
ohh.....I got it. Ok this is a valid fix. Could You rebase and fix the conflicts. And then we are good to go 👍 |
vkallore
commented
Dec 2, 2019
Resolved the conflicts. |
Summary
Fixes#914
Had raiesed an issue #914 on missing rel="noreferrer noopener" for links opening in new tab/window and done the fix with 'noopener' for links with
_blank. Thought not to add 'noreferrer' as it might be useful for referrer info.What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx], where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:
libdirectory.