Closed
Bug 255837
Opened 20 years ago
Closed 20 years ago
Popup blocker message persists across different URLs
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: skydaemon80, Assigned: bugs)
Details
(Keywords: fixed-aviary1.0, regression)
Attachments
(1 file)
4.56 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.2) Gecko/20040816 Firefox/0.9.1+
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.2) Gecko/20040816 Firefox/0.9.1+
The yellow popup information bar persists across different visited URLs even
after leaving a Web site whose popup window was blocked.
Reproducible: Always
Steps to Reproduce:
1. Ensure that the "Block popup windows" option is checked in the "Web Features"
panel of the Options dialog box (Tools | Options).
2. Use the location bar to jump to <http://www.cnn.com>. A popup window should
be blocked by Firefox, and the popup info bar should appear.
3. Visit other Web sites that do not trigger popup windows. Examples are:
Mozilla home <http://www.mozilla.org>
Inside Firefox <http://weblogs.mozillazine.org/ben/>
The Burning Edge <http://www.squarefree.com/burningedge/>
Try entering the URL in the location bar or clicking a bookmark.
Actual Results:
Regardless of whether the Web site was visited by manually entering its URL in
the location bar or clicking a bookmark item, the popup info bar remains. In
addition, clicking on it will show "Allow popups for www.<hostname>.com", where
<hostname> is the host name portion of the current URL.
Expected Results:
If the newly-visited Web site does not open popup windows, then the popup
information bar should disappear upon leaving the Web site whose popup window
was blocked by Firefox.
Currently, the popup info bar will only disappear after reloading the current
Web page that does not trigger a popup window.
I can confirm this on Windows XP
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040816
Firefox/0.9.1+
Flags: blocking-aviary1.0PR?
Comment 2•20 years ago
|
||
I imagine this was caused by the fix for bug 255162
Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
Flags: blocking-aviary1.0PR?
Flags: blocking-aviary1.0PR+
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0+
Assignee | ||
Comment 3•20 years ago
|
||
Assignee | ||
Comment 4•20 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Keywords: fixed-aviary1.0
Verified on the 2004-08-20 Firefox build.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•