window.open( ) function doesn't work

VERIFIED INVALID

Status

SeaMonkey
General
VERIFIED INVALID
16 years ago
13 years ago

People

(Reporter: Anthony DiSante, Assigned: asa)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126

On this page:

http://www.wired.com/news/mac/0,2125,56674,00.html

Click one of the thumbnail images midway down on the left, and nothing happens.
 It doesn't matter whether I have unrequested popups blocked or not.  I viewed
the source for their "popChild( )" function and it appears to just call
window.open( ).

So I get no popup, in Mozilla 1.2 and Netscape 6.2... but the popup does work in
Opera 6.05 and IE 6.0.2800.blahblahblah.etc.whatever.somemore.

So I don't know whether this is a bug, or if the code on the wired.com page is
buggy.  If it *is* buggy website design, I'll be glad to contact wired about it,
but I wanted to check here first.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Any errors in the JS console?
(Reporter)

Comment 2

16 years ago
Nope, no errors in the JS console.

On an unrelated note (I just saw this for the first time), every time I
mouseover the Tools menu, it gives an "element has no properties" JS error on
line 128 of chrome://cookie/content/cookieNavigatorOverlay.xul.  Guess I'll go
report that one.

Comment 3

16 years ago
There was a parser error in 1.2. Please upgrade to 1.2.1 and tell if that
improves the matter.

(And please search for duplicates of the cookieNavigatorOverlay.xul JS error
before filing a bug on it.)
(Reporter)

Comment 4

16 years ago
Nope, the problem persists in 1.2.1.

Comment 5

16 years ago
The popups WORKFORME using Mozilla trunk build 20021204xx WinNT.

This isn't a JS Engine issue. Reassigning to Browser-General until
we can get further information.

Anthony:

1. If the Mozilla Profile Manager doesn't already come up autmatically,
   you can force it to by launching Mozilla from a console window like this:

       [(path to Mozilla)] ./mozilla -profilemanager

   Once that comes up, click on "Create Profile". Does the problem
   go away if you run Mozilla under a brand-new profile?


2. (Only if the anwswer to 1. is "No"): if you get a chance, could you
   try a trunk Mozilla build? Does that show the problem, too, or only 
   the 1.2 and 1.2.1 builds? Thanks -
Assignee: rogerl → asa
Component: JavaScript Engine → Browser-General
QA Contact: pschwartau → asa
(Reporter)

Comment 6

16 years ago
I just discovered that my banner-ad-blocking proxy program also blocks pop-up
windows.  So it's not a Mozilla problem at all.  Sorry for the trouble.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID

Comment 7

16 years ago
Anthony: thanks! Marking Verified -
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.