Closed Bug 256200 Opened 21 years ago Closed 21 years ago

popup blocker incorrectly blocks while page is still loading

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 101190

People

(Reporter: zenervation, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040814 Firefox/0.9.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040814 Firefox/0.9.0 If you click a link that opens a new window on a page which is still being layed out, the popup blocker will block it incorrectly. On the example URL, the page is layed out incorrectly while the page is still loading, and then snaps into position. (this can be a bit hit-n-miss, you may have to clear the cache and restart the browser for the slow layout to happen) - If you click on the 'forums' link while it is still layed out incorrectly, it is blocked incorrectly. - Using the "show 'http://www.thewebsite.com" also breaks - instead of opening it, it blocks it again, causing that entry to be in the show menu twice. Reproducible: Always Steps to Reproduce: 1. Load the example URL 2. While the page is still being layed out (the content area is side-by-side with the header, instead of below) click on the 'forums' link 3. Click on 'show http://www.simlish.com/forum/' in the popup blocked bar that appears. Actual Results: - The new window was blocked incorrectly, and the popup blocked bar appeared. - When following step 3, instead of opening the window, it is blocked again. Expected Results: The window should open properly in the first place, and even if it is not, the "show http://www.thewebsite.com" should always work. This can be hard to reproduce. One way I've found to reproduce it is to create a new profile to visit the site.
*** This bug has been marked as a duplicate of 101190 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.