1801680 - [meta] Cookie Banner Handling Desktop UI v2

Status: NEW

(Core :: Privacy: Anti-Tracking, enhancement, P3)

Description

[[e-mail]]

Additional scope we would like to get in beyond Fx110 MVP:

Update Door Hangar to include a "Site not Working" and "Please Support This Site in the Future"

The Glean Code is new but the UI element itself can be recycled from the ETP Toggle

Comment 1

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Note: the v2 scope we want to capture here goes beyond what's listed in the description. See the child bugs under this metabug for an up-to-date list of issues in scope.

Comment 3

[[e-mail]]

Attachment: data-review.txt

Comment 4

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Comment on attachment 9314042 [details]
data-review.txt

Since this is sensitive (Category 3) data collection, the next step is to escalate to legal.

There is a new process to handle this, outlined here: https://wiki.mozilla.org/Data_Collection#Step_3:_Sensitive_Data_Collection_Review_Process

I forgot this new process existed, sorry I haven't mentioned it sooner. I haven't run through this new process before, so the data-stewards channel is probably a good place to ask any questions about next steps. Probably you'll just need to get a few more approvals in the existing data collection one-pager.

Comment 5

[[e-mail]]

Comment from Nneka confirming the data-review is r+:

Hi Cameron,
Thanks for your time yesterday. As you mentioned yesterday, there is no change from what we reviewed late last year and approved so that same approval should carry forward.

Best,
Nneka

Comment 6

[[e-mail]]

Comment on attachment 9314042 [details]
data-review.txt

r+ from Nneka and other Data Stewards as covered in this doc: https://docs.google.com/document/d/1hoW838Yyk73GQGoCSN9bfOi4YPR9E9B2VUlRFLEa-MA/edit?usp=sharing

See Comments for Nneka's specific reply

Comment 7

[[e-mail]]

Spoke with Paul, Arturo, and Jared concerning a dangling state where "detectOnly" never disables for certain user profiles.

Arturo mentioned how this is handled in the android implementation with guidance from this pr: https://github.com/mozilla-mobile/fenix/pull/28824

For FX111 there is no capacity to do anything, but I am filing a bug for Fx113 to ensure similar behavior is implemented for desktop.

In the meantime I think it best we use this as an opportunity to see if their is a feature performance hit that could occur in this dangling case.