Closed Bug 179769 Opened 22 years ago Closed 22 years ago

The built-in pop-up blocker sometimes blocks and sometimes allows the same sites

Categories

(Camino Graveyard :: General, defect)

Product:
Camino Graveyard
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: daytona63, Assigned: saari)

References

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021104 Chimera/0.6 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021104 Chimera/0.6 I've hosted some pictures at <homepage.mac.com>. If you are familiar with the site, you know that you can click on a picture, or click on the "Start Slideshow" button to start a manual slideshow. This all works via JavaScript, I believe. Anyways, it will work for awhile, then eventually when I try to start just such a slideshow at some later point, it won't work. Turning off the pop-up blocker does make it work. I'm not familiar with how a pop-up blocker works, but it is strange that it can be so fickle. Reproducible: Sometimes Steps to Reproduce: 1. Simply click on a picture or "Start Slideshow" 2. 3. Actual Results: Chimera did not load the slideshow Expected Results: It should (somehow) know that this pop-up window is legit all the time, not just some of the time.
Dup of bug 179768.
*** Bug 179768 has been marked as a duplicate of this bug. ***
Does it depend on the timing of your clicks? The popup blocker has a 1-second window after pageload during which window.open is denied.
In reply to the post by Simon Fraser, "Does it depend on the timing of your clicks? The popup blocker has a 1-second window after pageload during which window.open is denied." No, I don't think it depends on the timing of the clicks, meaning that I'll click on the link well after the initial window opens, and the window that should pop up does not. Of note, this does seem to happen much less now, with it only being a rare problem.
Tom, can you still reproduce this problem using a current nightly build? If so, please provide a specific example URL.
Can anyone reproduce this bug with a current build? (going once... going twice...)
ok then... resolving WFM
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.