For the new beta2, we want to make sure that anti-phishing doesn't start working (via Google honoring our client code), since the UI is not really shippable currently. Come to think of it, we might just want to disable it across-the-board until the UI is good enough to use; anyone who wants to use it currently would already have to hack the prefs to choose another client code.
9 years ago
Created attachment 363215 [details] [diff] [review] Turns off phishing and malware detection I think we should just land this unconditionally and then turn it back on once we get the UI "shippable".
Assignee: nobody → alqahira
Status: NEW → ASSIGNED
Attachment #363215 - Flags: superreview?(stuart.morgan+bugzilla)
Attachment #363215 - Flags: superreview?(stuart.morgan+bugzilla) → superreview+
Comment on attachment 363215 [details] [diff] [review] Turns off phishing and malware detection sr=smorgan, but stick in a comment since it's weird to have comments saying we are enabling them right above prefs that disable them (even if it's temporary)
Checked in with a comment explaining why they are disabled/false now.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.