Closed
Bug 187904
Opened 23 years ago
Closed 22 years ago
Popup window (after prompt) should not be blocked !
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 155351
Camino0.8
People
(Reporter: nicolas, Assigned: mikepinkerton)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.0.1) Gecko/20030105 Chimera/0.6+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.0.1) Gecko/20030105 Chimera/0.6+
In the page at http://www.fri-tic.ch/javascripttest.html, when popup window
blocking is ON, the popup window of first link is blocked, but not the one on
second link.
Reproducible: Always
Steps to Reproduce:
Click on both links
Actual Results:
On click on the first link, after confirmation, the popup window is blocked (it
doesn't appear). On click of the second link (without confirmation) the popup
window appears.
Expected Results:
Either links should behave the same, i.e. or both should open the popup window
or both should block it (first solution preferred).
Comment 1•22 years ago
|
||
this WFM in mozilla trunk but not camino.... as such marking new so it gets on
the radar, but I don't know what the opinion of the camino devs as to this being
intentional or not
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•22 years ago
|
||
bug 202189 is filed on alert and may be a dupe of this one
Summary: Popup window should not be blocked ! → Popup window (after prompt) should not be blocked !
| Assignee | ||
Comment 5•22 years ago
|
||
wonder if this is another casualty of that other dom pref we set. i'll go turn
that off and see how that affects these bugs.
Assignee: saari → pinkerton
Target Milestone: --- → Camino0.8
| Assignee | ||
Comment 6•22 years ago
|
||
fixed with 155351
*** This bug has been marked as a duplicate of 155351 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Comment 7•22 years ago
|
||
*** Bug 202189 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•