-
-
Notifications
You must be signed in to change notification settings - Fork 203
Cookies 2025 chapter #4276
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.
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
base: main
Are you sure you want to change the base?
Cookies 2025 chapter #4276
Conversation
…hive.org into cookies-2025
|
I've staged the chapter here: https://cookies-2025-dot-webalmanac.uk.r.appspot.com/en/2025/cookies Unfortunately staging isn't automated so reach out if you want it re-staged at any time. |
Let's add the SQL in a separate PR please. That way it can be merged ahead of the chapter and keeps this PR small. |
|
Thank you @tunetheweb for the edits, staged version, and comments, much appreciated! |
JannisBush
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall it looks promising, but I have a lot of small questions/remarks.
|
|
||
| The observations from this chapter confirm the conclusions from last year's analysis: | ||
| - A majority (60%) of cookies encountered on the web are third-party cookies and popular websites create them the most. | ||
| - Most popular cookies can be linked to advertising, tracking, and analytics use cases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Maybe add that most third-party cookies come from very few sites. Not sure if we have a query for that, but probably we could make a query to show that 90% of third-party cookies belong to only 100 sites (or something similar).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| {{ figure_markup( | ||
| image="same-site-mobile.png", | ||
| caption="`SameSite` attribute for cookies on mobile client.", | ||
| description="Shows the prevalence of the `SameSite` attribute and its value for both first-party and third-party cookies on mobile clients. We see very similar results as for desktop clients. 3% of first-party cookies set the `SameSite` attribute to `Strict`, 19% use `SameSite=Lax` (which is the default), 11% set the value to None and 63% do not specify the value of `SameSite`. Nearly 100% of third-party cookies set the `SameSite` attribute to `None`, in order for these cookies to be sent in a cross-site context.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Data is quite different from data the security chapter team has: https://docs.google.com/document/d/1PsuoanrDsTxTpNrf8VBAx_IxWVw6BTuCG1DnDzhWj00/edit?disco=AAABxmaWuaY
Is either query incorrect or can it be explained with top1m vs all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same issue seems to be affecting 2024: https://almanac.httparchive.org/en/2024/cookies#fig-10 vs https://almanac.httparchive.org/en/2024/security#fig-12
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure and I don't have much time to investigate more here, maybe @ChrisBeeti or someone else can look into that.
The cookies chapter use the cookies returned by the $WPT_COOKIES (i.e., grabbed directly from the cookies jar, so only valid cookies parsed by Chrome). maybe the security chapter relies on HTTP requests?
|
@yohhaan what's the latest with this? I don't see any response to the feedback and it's still in draft status. |
|
Comment from @JannisBush: Queries missing |
I had left for vacation for the holidays just after the review was posted. I have now addressed and resolved most of the comments that were about the phrasing and text details. Remaining comments are essentially about the SQL queries and figures on which I have tagged @ChrisBeeti, analyst for the chapter. Also removing the draft mode. |
Hi!
This is a (draft for now) pull request with the content for the 2025 Cookies chapter (#4069). To be more efficient, the content has been drafted directly in markdown (no Google Docs). Feel free to edit on the cookies-2025 branch directly, or leave comments in your review on this PR.
Staged version: https://cookies-2025-dot-webalmanac.uk.r.appspot.com/en/2025/cookies
Staged version of home page quotes and stat: https://cookies-2025-dot-webalmanac.uk.r.appspot.com/en/2025/?feat=cookies#featured-chapter
So far, the 2025 chapter is pretty similar to last year's analysis IMO, although I have pointed out to some differences I noticed. Some suggestions or ideas if people have some time to help:
{# TODO ... #}comments that I left in the sections that I felt could use more.ToDos/Next steps:
Thanks!
Fixes #4069