Closed
Bug 508727
Opened 15 years ago
Closed 15 years ago
Disable the "Report Phishing Page…" menu item when safebrowsing is off
Categories
(Camino Graveyard :: Security, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Camino2.0
People
(Reporter: alqahira, Assigned: murph)
References
Details
(Whiteboard: l10n [camino-2.0])
Attachments
(1 file, 1 obsolete file)
4.79 KB,
patch
|
stuart.morgan+bugzilla
:
superreview+
|
Details | Diff | Splinter Review |
Per discussion at this morning's meeting, the "Report Phishing Page…" menu item should be disabled when safebrowsing is off. The menu item should also show an appropriate tooltip when _disabled because safebrowsing is off_ (see "Check for Updates…").
Flags: camino2.0b4+
Reporter | ||
Updated•15 years ago
|
Whiteboard: l10n
Assignee | ||
Comment 1•15 years ago
|
||
Note that there appears to be a problem on Leopard, with tooltips not displaying on menu items under the new Help menu. I verified using F-Script that the tooltip does properly set and unset itself as the safe browsing preference changes. Rather than wait for a workaround, I'm submitting this now to get the strings in for l10n.
Assignee: nobody → murph
Attachment #397350 -
Flags: review?
Reporter | ||
Updated•15 years ago
|
Attachment #397350 -
Flags: review? → review?(trendyhendy2000)
Reporter | ||
Comment 2•15 years ago
|
||
Comment on attachment 397350 [details] [diff] [review] Patch hendy said he's up to the challenge of this code review. As for the string: > +"PhishReportingDisabledToolTip" = "Safe browsing must be enabled to report phishing pages."; Aside from some URL pieces on the website and mentioning on some web pages that we use Google's SB service , we don't use the term "safe browsing" anywhere. "PhishReportingDisabledToolTip" = "“Warn me when visiting potentially malicious sites” must be enabled to report phishing pages."; is kind of a mouthful, but that's the only name we have for the feature in the Camino UI (bonus: it's the name of the pref if the user goes poking through the UI, and the pref name will come up in a Google search of cbo once the safebrowsing page gets linked and crawled). We could also do something like "Phishing and malware protection must be enabled to report phishing pages" but that uses phishing twice and still doesn't help match you with a string in the prefs UI.
Updated•15 years ago
|
Attachment #397350 -
Flags: review?(trendyhendy2000) → review+
Comment 3•15 years ago
|
||
Comment on attachment 397350 [details] [diff] [review] Patch I agree with Smokey wrt the tooltip string. > if (action == @selector(reportPhishingPage:)) { ... } Somewhere in this block there needs to be a check for [browserController shouldSuppressWindowActions]. We don't want to users to be able to report a site while customizing their toolbar. If I set browser.safebrowsing.enabled to false and browser.safebrowsing.malware.enabled to true in about:config, I'm still able to report a site. Shouldn't that be disabled, since phishing detection is disabled? Maybe use eSafeBrowsingPhishingListType in the check. r+ with those things addressed.
Assignee | ||
Comment 4•15 years ago
|
||
Thanks for the review Hendy. All of your comments were addressed, thanks for catching those aspects. As for the tooltip, I agree myself about the wording. Using safe browsing didn't sit totally right with me either, the only reason I talked myself into keeping it was that we use it on the error overlay as the "more information" link title. I have changed it to the first string Smokey mentioned for now.
Attachment #397350 -
Attachment is obsolete: true
Attachment #398151 -
Flags: superreview?(stuart.morgan+bugzilla)
Comment 5•15 years ago
|
||
Comment on attachment 398151 [details] [diff] [review] Patch, v2 sr=smorgan
Attachment #398151 -
Flags: superreview?(stuart.morgan+bugzilla) → superreview+
Reporter | ||
Comment 6•15 years ago
|
||
Landed on cvs trunk and 2_0 branch. Filed bug 514236 on the issue in comment 1.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Whiteboard: l10n → l10n [camino-2.0]
You need to log in
before you can comment on or make changes to this bug.
Description
•