97396 - [Regression] Mozilla stops creating new browser windows after failing tv guide js

Status: RESOLVED WORKSFORME

(SeaMonkey :: UI Design, defect, P3)

Description

[Ben Ruppel]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0b; Windows NT 5.0)
BuildID:    2001082803

This was okay with Sunday's build, and then on Monday (08/27) a nasty bug came 
up.  It's a real bummer because it can ruin your whole browsing session.  If 
you go to a listings table in www.tvguide.com/listings/ (you have to give them 
your info for a listing) you can normally click on a show title and a little 
window will pop up with a further description. Now, when I do this the browser 
acts funny (the throbber starts, then becomes blank, the navigation buttons go 
wacky and the stop button disappears).  No new window pops up, and instead, 
mozilla can't open a new browser window in any way until it's restarted.  ctrl-
N, File>New Navigator Window... nothing works.  
Here is an example of the js code that apparently causes the problem:
javascript:cl(63151,952433);

Reproducible: Always
Steps to Reproduce:
1.go to www.tvguide.com/listings/ and fill out stuff to get to a listings table
2.click on a show title

Actual Results:  no description window opens.  mozilla starts acting weird, 
including strange navigation and throbber behavior and the inability to open 
any new browser windows.  this makes using the bugzilla helper a pain, as you 
can't open a submission form :)

Expected Results:  a little description window should open.

This is fresh, it just started happening.  I really hope someone can find the 
problem easily.

Comment 1

[Matthias Versen [:Matti]]

wfm with win2k build 20010828.. (1h old CVS)

Comment 2

[Chase Tingley]

WFM Linux cvs build from late 20010827.

Comment 3

[Ashley Bischoff (blog at handcoding.com)]

WFM 2001082803 on Win2k (your precise build). Marking WFM as per my experience
and other comments. You could try a new profile.

Also: You're not using a proxy, right?

Comment 4

[Ben Ruppel]

Right, I'm not using a proxy.  I think the problem is that there's more to the
reproducability than I have recorded here (It happened to me twice on two
separate days).  If I can get it to happen again and figure out what triggered
it, I'll post the info.

Comment 5

[Ben Ruppel]

Okay, this happened to me today with the newest build and without tv guide.  Of
course, it's hard to figure out exactly what page made it start up...

It's hard to reproduce.  In any case, this bug seems like a dupe of some other
bug that's been fixed/whatever at some point along the way.  

Comment 6

[Ben Ruppel]

Hey, this just happened to me again with the 2001090408 build on this page:
http://www.gamestar.de/magazin/qcdoom3.htm  I clicked on a picture, which was
scripted to show in a new page.  I closed that picture page, and then the other
pictures did not work.  Then no new windows were openable for the rest of the
session.  

Comment 7

[Ben Ruppel]

I got a confirmation on this bug from the newsgroups (an OS 9 user).  
They got this problem with www.Jish.nu

If I change the name to "Mozilla stops displaying new windows after js" can we
reopen this?  I don't want to upset anyone, so I'm asking before I try.  I
couldn't find any dupes.

Another good point is that new windows will be listed under tasks, they'll just
be invisible.

Comment 8

[Henri Sivonen (:hsivonen)]

This is a real problem. Happens on Mac OS X, too. I haven't verified what
triggers it, but the symptoms are real.

Comment 9

[R.K.Aa.]

*** Bug 99827 has been marked as a duplicate of this bug. ***

Comment 10

[Asa Dotzler [:asa]]

->xpapps

Comment 11

[Boris Zbarsky [:bzbarsky]]

*** Bug 100928 has been marked as a duplicate of this bug. ***

Comment 12

[Paul Chen]

Marking p3, critical, and mozilla1.0. CC-ing jag. I will be more proactive on
this bug once I can see some reproducible test cases. This isn't meant as a
brush off, but as default owner of xpapps bugs, I get a ton of bugs. ;-)

Comment 13

[Ben Ruppel]

I'm having a very hard time reproducing this bug reliably.  Clicking on js till
the cows come home won't trigger it, yet it'll pop up when you least expect it.

Comment 14

[patrick]

I have noticed that in mozilla 0.9.5, once the bug is "activated" (can't open
new windows) the open new tab feature (CTRL-T) still works. So it seems to me
that this feature must share a lot of code with the open new window (CTRL-N) and
javascript window.open function and hence that code would appear to be sound. It
is also weird that this bug is only ever triggered by the javascript window.open
command and never by the open new window menu option (i.e right click on link
and open in new window). It also seems weird that the resize parameters of the
javascript command are executed fine, since a new mozilla process will open a
window with the size specified in the offending javascript window.open function
call.

Comment 15

[Ben Ruppel]

Another symptom of this bug: right-click context menus start to take a long time
to show up, or don't show up at all.

Comment 16

[Paul Chen]

Umm, need more test cases, moving to mozilla1.1. I'll move it forward once I 
can get a reproducible test case

Comment 17

[patrick]

I have tried to find find a way to reliably trigger the bug and have found a way
that always works for my system (linux dual pIII 500). Start up a fresh browser
and open two tabbed windows, in the first load:
http://news.bbc.co.uk/
In the second load:
http://www.spacesurfer.com/wceleb/
This page has a floatig javascript banner and a background popup window that
sometimes appears. Once the main page has loaded but the browser still appears
to be loading the javascript stuff, click on the first tab and select the
"Launch Console for latest Audio/Video" graphic link that appears on the right
hand blue menu/bar. This link should lauch a new subwindow, but will fail and
trigger the bug instead.

Comment 18

[patrick]

This bug which used to happen all the time on my machine has disappeared in
0.9.6. Well at least it hasn't been triggered at all since I installed the new
mozilla yesterday

Comment 19

[Ben Ruppel]

Yes, this hasn't popped up on me in nightlies for a while.  Hopefully it was
fixed by some other changes.

Comment 20

[Ashley Bischoff (blog at handcoding.com)]

-> WFM?

Comment 21

[Matthias Versen [:Matti]]

marking worksform

-> This should be fixed by another checkin (I can't find the bug# at the moment)