From 3fdf7ec9351f9ee8e62648146a7e73e7a6196d5f Mon Sep 17 00:00:00 2001
From: kaushik95 <kaushik.19995@gmail.com>
Date: Fri, 13 Sep 2024 05:11:56 +0530
Subject: [PATCH] Navigator: cookieEnabled warning regarding Safari is outdated
 #32845 (#35725)

* Navigator: cookieEnabled warning regarding Safari is outdated #32845

Signed-off-by: Kowshik BV <kowshik.bv@fmr.com>

* Update index.md

Removed note section as it is not needed.

Signed-off-by: kaushik95 <kaushik.19995@gmail.com>

---------

Signed-off-by: Kowshik BV <kowshik.bv@fmr.com>
Signed-off-by: kaushik95 <kaushik.19995@gmail.com>
---
 files/en-us/web/api/navigator/cookieenabled/index.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/files/en-us/web/api/navigator/cookieenabled/index.md b/files/en-us/web/api/navigator/cookieenabled/index.md
index 42a28473c5a9278..3ebb743258ac194 100644
--- a/files/en-us/web/api/navigator/cookieenabled/index.md
+++ b/files/en-us/web/api/navigator/cookieenabled/index.md
@@ -16,9 +16,6 @@ The property is read-only.
 
 A boolean.
 
-> [!NOTE]
-> When the browser is configured to block [third-party cookies](/en-US/docs/Web/Privacy/Third-party_cookies), and `navigator.cookieEnabled` is invoked inside a third-party `<iframe>`, it returns `true` in Safari and IE (while trying to set a cookie in such scenario would fail). It returns `false` in Firefox and Chromium-based browsers.
-
 > [!NOTE]
 > Web browsers may prevent writing certain cookies in certain scenarios. For example, Chrome-based browsers, as well as some experimental version of Firefox, does not allow creating cookies with [`SameSite=None`](/en-US/docs/Web/HTTP/Headers/Set-Cookie#samesitesamesite-value) attribute, unless they are created over HTTPS and with `Secure` attribute.