Skip to content

[NEW] Add ref="noopener noreferrer" to Markdown links#7327

Merged
rodrigok merged 1 commit intoRocketChat:developfrom
jangmarker:add-noreferrer-to-links
Jun 30, 2017
Merged

[NEW] Add ref="noopener noreferrer" to Markdown links#7327
rodrigok merged 1 commit intoRocketChat:developfrom
jangmarker:add-noreferrer-to-links

Conversation

@jangmarker
Copy link
Copy Markdown
Contributor

Links created by autolinker already have these attributes. However, links created via Markdown title or <link|title> didn't have these.

@RocketChat/core

Links created using Markdown syntax leak channel names because they do not have ref="noreferrer". Links created by autolinker have noreferrer and noopener. Add these two attributes to links created via Markdown.

Links created by autolinker already have these attributes. However, links created via Markdown [title](link) or <link|title> didn't have these.
@karlprieb
Copy link
Copy Markdown
Contributor

Thank you for your contribution 👍

@jangmarker
Copy link
Copy Markdown
Contributor Author

Thanks for approving! :-) I cannot merge myself, will this be merged by someone according to some process?

@karlprieb
Copy link
Copy Markdown
Contributor

Yes, probably @rodrigok or @engelgabriel will merge this PR :)

@rodrigok rodrigok added this to the 0.58.0 milestone Jun 30, 2017
@rodrigok rodrigok merged commit 747061f into RocketChat:develop Jun 30, 2017
@pitamar
Copy link
Copy Markdown
Contributor

pitamar commented Aug 3, 2017

Hi,
I think it's supposed to be rel="noopener noreferrer"
https://www.w3schools.com/TAGs/att_a_rel.asp

Am I wrong?
Thanks
Itamar

jangmarker added a commit to jangmarker/Rocket.Chat that referenced this pull request Aug 3, 2017
Follow-up to RocketChat#7327 fixing the usage of "ref" to "rel" as pointed out
by @pitamar.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants