Status Update
Comments
jo...@google.com <jo...@google.com>
jo...@google.com <jo...@google.com> #2
I discussed this with the Classroom team and they're messaging to affected developers and will track progress internally for now.
It's likely that many of the add-ons are affected, mostly with identity/GSI use cases.
Let's keep this bug as a general tracker for Classroom add-ons and follow up in a few weeks to check in on the progress.
ds...@google.com <ds...@google.com> #3
Just following up here with a recap. We synced with the Privacy Sandbox team and determined that the existing Privacy Sandbox API's aren't currently able to resolve this breakage, at least before the 1% 3P cookie deprecation. For now, we will continue to collaborate to find a solution.
I have summarized the state of Classroom add-ons impact in go/cookieless-classroom-add-ons-summary and the investigation into Privacy Sandbox API's in go/cookieless-classroom-add-ons.
ds...@google.com <ds...@google.com> #4
Following up here that we recommended the
ds...@google.com <ds...@google.com> #5
Just updating this for clarity of deprecation trial reviewers.
- The technical issue and background is described in
.go/cookieless-classroom-add-ons - An example failure case is documented in
for CK12, but all add-ons will be the same, as they have the same sign-in requirements.go/classroom-add-on-3pc-failure-example - The normal flow for add-ons is shown in
for additional contextgo/add-on-sso-flow
Description
Thank you for taking the time to report a broken web experience related to the blocking of third party cookies. Please follow the instructions below to report your issue.
The Chrome Privacy Sandbox team
Instructions: Please ensure that this submission is for one specific issue. If you have multiple breakage issues to report, please file them separately to allow for ease of triage by our team.