From c531fc309e848199712d6051ae7939ba9ec61368 Mon Sep 17 00:00:00 2001 From: Dongsung Kim Date: Thu, 11 Feb 2021 01:37:48 +0900 Subject: [PATCH] : Merged the two similar notes, added more links. --- files/en-us/web/html/element/a/index.html | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/files/en-us/web/html/element/a/index.html b/files/en-us/web/html/element/a/index.html index e408f96cc35e06c..85777efb81723ea 100644 --- a/files/en-us/web/html/element/a/index.html +++ b/files/en-us/web/html/element/a/index.html @@ -90,11 +90,7 @@

Attributes

-

Note: When using target, add rel="noreferrer noopener" to avoid exploitation of the window.opener API.

-
- -
-

Note: Setting target="_blank" on <a> elements implicitly provides the same rel behavior as setting rel="noopener". See browser compatibility for support status.

+

Note: Setting target="_blank" on <a> elements implicitly provides the same rel behavior as setting rel="noopener" which does not set window.opener. See browser compatibility for support status.

{{HTMLAttrDef("type")}}
@@ -319,7 +315,7 @@

Security and privacy

<a> elements can have consequences for users’ security and privacy. See Referer header: privacy and security concerns for information.

-

Using target="_blank" without rel="noreferrer" and rel="noopener" makes the website vulnerable to {{domxref("window.opener")}} API exploitation attacks (vulnerability description), although note that, in newer browser versions setting target="_blank" implicitly provides the same protection as setting rel="noopener". See browser compatibility for details.

+

Using target="_blank" without rel="noreferrer" and rel="noopener" makes the website vulnerable to {{domxref("window.opener")}} API exploitation attacks (vulnerability description), although note that, in newer browser versions setting target="_blank" implicitly provides the same protection as setting rel="noopener". See browser compatibility for details.

Accessibility