Skip to content

Clear-Site-Data integration #160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 20, 2025
Merged

Clear-Site-Data integration #160

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3a3ebab
Clear-Site-Data integration
martinthomson May 16, 2025
e486146
Merge branch 'main' into csd-impression
martinthomson May 16, 2025
02cbd8f
This is not English text any more
martinthomson May 19, 2025
77b3194
brackets
martinthomson May 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 46 additions & 0 deletions api.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -888,6 +888,50 @@ excludes expired [=impressions=] from [=attribution=]. However, the
[=user agent=] should not retain expired [=impressions=] indefinitely.


### `Clear-Site-Data` Integration ### {#impression-store-clear}

The [:Clear-Site-Data:] field [[CLEAR-SITE-DATA]]
gives sites the ability to remove state maintained by a [=user agent=].
The \``"impressions"`\` type is added to the list of recognized types,
Copy link
Collaborator

@apasel422 apasel422 May 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just checking: Are we intentionally rendering the backticks here?

Copy link
Member Author

@martinthomson martinthomson May 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apparently, that is house style. That is what you get with [:Clear-Site-Data:] as well:

image

(I think that it's gross, but who am I to suggest that?)

defined in [[CLEAR-SITE-DATA#header]].

When the [CLEAR-SITE_DATA#abstract-opdef-clear-site-data-for-response|clear site data for response]] algorithm is invoked,
if the list of types [=set/contains=] \``"impressions"`\`,
the [=clear impressions for a conversion site=] is invoked,
passing the |origin|.

To <dfn>clear impressions for a conversion site</dfn>,
given an [=origin=] |origin|,
run these steps:

1. If |origin| is not a [=tuple origin=] with a [=scheme=] of `https`,
return.

1. Let |site| be the value returned
by invoking [=registrable domain|obtain a registrable domain=],
passing the [=host=] part of the [=tuple origin|origin tuple=].

1. For each stored [=impression=], |impression|,
in the [=impression store=]:

1. If |impression| has an [=impression/Intermediary Site=] equal to |site|,
[=set/remove=] |impression| from the [=impression store=] and continue.

1. If |impression| has a [=impression/Conversion Sites=] [=set=]
that does not [=set/contain=] the value |site|, continue.

1. If the [=set/size=] of the [=impression/Conversion Sites=] [=set=]
for the |impression|
is greater than one [=site=],
[=set/remove|remove=] |site| from [=impression/Conversion Sites=]
and continue.

1. Otherwise, [=set/remove=] |impression| from the [=impression store=].

<p class=note>This process does not remove impressions
that are saved with an empty [=set=] of [=impression/Conversion Sites=].


### Site Names ### {#site-name-algorithm}

The [=impression store=] saves information
Expand Down Expand Up @@ -2228,6 +2272,8 @@ The privacy architecture is courtesy of the authors of [[PPA-DP]].


<pre class=anchors>
urlPrefix: https://fetch.spec.whatwg.org/; spec: html; type: dfn
text: request origin; url: #concept-request-origin
urlPrefix: https://html.spec.whatwg.org/; spec: html; type: dfn
text: host; url: #concept-origin-host
text: obtain a site
Expand Down
Loading