From 150ffbfaec733596aa5f6b21127701ce14490678 Mon Sep 17 00:00:00 2001 From: Aaron Selya Date: Tue, 2 Apr 2024 09:43:33 -0400 Subject: [PATCH] Update proposals/hasCrossSiteAncestor.md Update to remove reference to Chrome Co-authored-by: Rob Wu --- proposals/hasCrossSiteAncestor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/hasCrossSiteAncestor.md b/proposals/hasCrossSiteAncestor.md index 8b952be9..ec506fc1 100644 --- a/proposals/hasCrossSiteAncestor.md +++ b/proposals/hasCrossSiteAncestor.md @@ -17,7 +17,7 @@ Allow extensions to utilize a hasCrossSiteAncestor boolean value when interactin **Related Issues:** [How do Partitioned cookies interact with browser extensions?](https://github.com/privacycg/CHIPS/issues/6) ## Motivation -[Chrome](https://github.com/privacycg/CHIPS/issues/40) is adding a cross-site ancestor bit value to partitioned cookies. +https://github.com/privacycg/CHIPS/issues/40 is adding a cross-site ancestor bit value to partitioned cookies. ### Objective To interact with partitioned cookies containing a cross-site ancestor chain bit correctly, extensions will need to have the ability to to specify a value (hasCrossSiteAncestor) that cooresponds to the value of the cross-site ancestor chain bit in partitioned cookies.