Closed
Bug 340866
Opened 19 years ago
Closed 19 years ago
Anti-phishing only works on the last opened window (fails otherwise)
Categories
(Toolkit :: Safe Browsing, defect)
Tracking
()
RESOLVED
FIXED
Firefox 2 beta1
People
(Reporter: johngraciliano, Assigned: tony)
References
()
Details
(Keywords: fixed1.8.1)
Attachments
(1 file)
|
1.94 KB,
patch
|
brettw
:
review+
bryner
:
approval-branch-1.8.1+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a3) Gecko/20060526 BonEcho/2.0a3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a3) Gecko/20060526 BonEcho/2.0a3
The "Web Forgery" signal is only given inside the last Bon Echo 2.0a3 window open that was opened. It does not show in any former window. This has nothing to do with the "tabs".
Reproducible: Always
Steps to Reproduce:
1. Have a Firefox 2.0a3 (A.K.A. Bon Echo) open.
2. Open another window.
3. Within the original window (or any previous window)open the "Google Safe Browsing Test Page," i.e., http://www.google.com/tools/firefox/safebrowsing/phish-o-rama.html
Actual Results:
No "Web Forgery" alert is given.
Expected Results:
The "Web Forgery" alert should come up! As it does *only* within the last opened window.
Also to reproduce:
1. Open a Bon Echo window.
2. Open a second window.
3. Close the second window.
4. Got to the test page (within the first window).
Comment 1•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a3) Gecko/20060529 BonEcho/2.0a3
Yep, that's true.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → 2.0 Branch
Comment 2•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060608 Minefield/3.0a1
Tested latest branch nightly (sorry, pasted wrong UA string) and also present in trunk.
Updated•19 years ago
|
Flags: blocking-firefox2?
Updated•19 years ago
|
Target Milestone: --- → Firefox 2 beta1
| Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Comment 3•19 years ago
|
||
Tony, remember to assign the bug to yourself before accepting the bug (I know that Bugzilla UI is confusing here)
Assignee: nobody → tony
Status: ASSIGNED → NEW
Flags: blocking-firefox2? → blocking-firefox2+
| Assignee | ||
Comment 4•19 years ago
|
||
So the problem was that all windows were sharing a nsIDocNavStartProgressListener instance and the callback would only work with the last opened window. Switching to separate instances fixes that.
Attachment #225292 -
Flags: review?(brettw)
Attachment #225292 -
Flags: approval-branch-1.8.1?(bryner)
Updated•19 years ago
|
Attachment #225292 -
Flags: review?(brettw) → review+
Comment 5•19 years ago
|
||
Comment on attachment 225292 [details] [diff] [review]
v1: use separate nav watcher per window
As I said earlier, blanket a=me for safe-browsing-only patches
Attachment #225292 -
Flags: approval-branch-1.8.1?(bryner) → approval-branch-1.8.1+
| Assignee | ||
Comment 6•19 years ago
|
||
Fixed on branch and trunk.
Updated•11 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•