Closed
Bug 1816470
Opened 3 years ago
Closed 1 month ago
Add check to ensure detectOnly Mode not enabled in dangling state
Categories
(Core :: Privacy: Anti-Tracking, enhancement)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: cboozarjomehri, Unassigned)
References
Details
Mimic Android implementation to ensure detectOnly mode disabled by default unless enable conditions met on browser start. (Implementation for ref: https://github.com/mozilla-mobile/fenix/pull/28824 )
-By default detectOnly mode is disabled
- Browser determines if detectOnly mode to be enabled by checking if CBH enabled preference set or timeout has passed
- When enabled will prompt user to opt-in to CBH on first appearance of banner
- detectOnly detects banner and begins onboarding flow
a) user communicates a preference (opt-in or opt-out of CBH) and detectOnly is disabled from now on
b) user exits off onboarding prompt without communicating opt-in/opt-out. detectOnly is disabled for 8 hours and then re-enabled to prompt the user again
Background: There us concern detectOnly mode could be left enabled even after a user expresses a preference for whether they want CBH enabled or not. This could lead to potential performance hits as the code continues to run needlessly in the background.
Comment 1•1 month ago
|
||
We are no longer pursuing CBH.
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•