-
Notifications
You must be signed in to change notification settings - Fork 55
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
TAG spec review of Bounce Tracking Mitigations #862
Comments
Just to clarify, I think this is intended to cover "bounce tracking mitigations" which is one part of the nav-tracking-mitigations repository. In particular, the spec is just this section of the doc: https://privacycg.github.io/nav-tracking-mitigations/#bounce-tracking-mitigations The privacycg chairs asked us to include it in this repo and due to bikeshed tooling support we could only have a single document in the repo. So the spec is a section within the larger report doc. Sorry for any confusion about this! |
Hi @wanderview @amaliev @jyasskin. We (@torgo @hadleybeeman @maxpassion and I) reviewed this in our virtual face-to-face this week. We're really happy to see this being worked on! The design looks good and well aligned with the privacy principles. What feedback have you had from other browsers in the PrivacyCG? It's great to see that you feel the proposal is aligned with what other implementers have done, and we would be even happier to see other implementers collaborating with you on documenting this behaviour – which would give clear guidance to web developers. ✨ We're looking forward to hearing more about your progress going forward. What are your thoughts about your next steps? |
Thank you! We agree that browser interop on this feature would be great and we intend to keep working on alignment with other vendors. Next steps for us:
The coming TPAC will be a good opportunity to discuss with other browser vendors. |
Sorry, missed answering this. We have official requests for feedback from other browser vendors here: mozilla/standards-positions#835 I don't want to speak for them, but I will say personally I think our interactions in privacycg on this feature have been positive. |
Hi @wanderview @amaliev @jyasskin. We are looking at this again in our W3C TAG breakout session. We are going to close this. We like the direction and design of this feature, but we note how early it is and are glad you're collaborating with other stakeholders — though we would like to see full consensus (which we understand comes later than positive interactions). We hope you continue to work on getting that consensus. Please do open a new review when the design (and consensus) is a bit more mature. |
FYI, @Trikolon and @bvandersloot mentioned at TPAC that Mozilla is implementing this bounce tracking mitigations feature in Firefox. |
こんにちは TAG-さん!
I'm requesting a TAG review of Bounce Tracking Mitigations.
With browser vendors now actively working to remove third-party cookies from the web, some platform trackers are moving to bounce tracking. This technique involves navigating to a tracker domain at the top level of a browser tab, setting or reading a first-party cookie, and then quickly redirecting away using a request that encodes the value of that first-party cookie. Sometimes the redirect is back to the original page and sometimes to a new site. In either case, bounce tracking semantically functions like setting a third-party cookie. This explainer outlines a proposal for mitigating the privacy impact of bounce trackers.
Further details:
You should also know that...
N/A
We'd prefer the TAG provide feedback as (please delete all but the desired option):
🐛 open issues in our GitHub repo for each point of feedback
The text was updated successfully, but these errors were encountered: