Closed Bug 1399798 Opened 7 years ago Closed 2 years ago

SafeBrowsing on Fennec: no "This isn't an attack site" button for users to report detection problems

Categories

(Toolkit :: Safe Browsing, defect, P3)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cynthiatang, Unassigned)

References

Details

Modify preferences:
 - urlclassifier.malwareTable: 
   replace words: shavar --> proto
 - urlclassifier.phishTable: 
   replace words: shavar --> proto

Steps to reproduce
 1. Launch Fennec
 2. Visit https://testsafebrowsing.appspot.com 
 3. Find "Should show a phishing warning:" and tap its "Link"
 4. Tap on "Ignore this warning" on the block page 

Expected result
 - After Step 4, there should be a "This isn't an attack site" button for user to 

Actual result
 - After Step 4, there is not a "This isn't an attack site" button for user to report a detection problem.
 - Video: https://goo.gl/1D42t6

Note: For Chrome on Android, there is a button to report a detection problem
Priority: -- → P3
Whiteboard: #sbv4-m10
Is this a regression or is the behavior the same on V2 and V4?
Hi François,
The behaviour is the same on V2 and V4. Does it mean that Fennec will not allow user to report a detection problem on V4? Thanks.

Version: Firefox 57.0a1 (2017-09-19)
Flags: needinfo?(francois)
(In reply to Cynthia Tang [:cynthiatang] from comment #2)
> The behaviour is the same on V2 and V4. Does it mean that Fennec will not
> allow user to report a detection problem on V4? Thanks.

Thanks for the confirmation Cynthia.

Since this is not a regression, I will remove it from milestone 10.

It will most likely be addressed when the UI is updated in bug 1400654.
Depends on: 1400654
Flags: needinfo?(francois)
Whiteboard: #sbv4-m10
Summary: SafeBrowsing v4 for Fennec - there is not a "This isn't an attack site" button for user to report a detection problem → SafeBrowsing on Fennec: no "This isn't an attack site" button for users to report detection problems
Whiteboard: #sbv4-m10
Whiteboard: #sbv4-m10

Fennec is EoS.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.