Closed Bug 88355 Opened 23 years ago Closed 23 years ago

window.open fails to open a new 2nd window (but loads the first fine)

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
VERIFIED DUPLICATE of bug 104769
Milestone:
mozilla0.9.6

People

(Reporter: stephend, Assigned: danm.moz)

References

Details

(Keywords: regression)

Attachments

(1 file)

simple javascript page with if, else if statement using window.open calls
876 bytes, text/html
Details 
Build ID: Trunk 2001-06-28-04, Windows 2000.

<stephend> who should I assign to?
<jst> assign it to danm
<jst> cc me

Summary: document.open fails to open a new 2nd window (but loads the first fine)

Steps to Reproduce: 

1.  Load the testcase.html and type either 'foo' or 'bar'. (Notice the page
loads in a new window, depending on the condition evaluated)
2.  Go back to the testcase.html, hit reload and type the other string you
haven't used yet.

Expected Results:

Both pages, http://www.mozilla.org/ and http://people.netscape.com/stephend/
should load in seperate pages.

Actual Results:

Moz doesn't load the 2nd page, but the throbber and progress meter keep going.
I'm half asleep, I'm using window.open calls, sorry. (changing summary)
Summary: document.open fails to open a new 2nd window (but loads the first fine) → window.com fails to open a new 2nd window (but loads the first fine)
Summary: window.com fails to open a new 2nd window (but loads the first fine) → window.open fails to open a new 2nd window (but loads the first fine)
This WorksForMe in Build 2001062804 in WinNT.

I see this, 2001062608 Linux trunk.  Throbber gets a groove on but nothing ever
happens; statusbar continues to read "Connected to bugzilla."

see this bug with build 2001062904 under Win95
Dan, I had a quick look at this last night and it looks like when we call
window.open() we end up calling into the window watchers open code which spins a
nested event loop but we never return from the wall into the window watcher,
mozilla kinda continues working but everything is happening from within that
nested event loop, or something. After running this testcase mozilla won't quit,
you haveto kill the process after the last window is closed since it won't go away.
  Yes, I see it. I doubt the problem is in the window opening code. It's normal 
to spin in that loop until the chrome has finished loading. I'll look at it, but 
the problem could be anywhere.
  Note that the the emphasis on two separate pages in the testcase is a bum 
steer. The content of the page being loaded is unimportant, and the prompt has 
nothing to do with it. Better testcase:

<html><body><script>
window.open("http://www.mozilla.org/");
</script></body></html>

My guess is that the page loading code running in the reload button's click event 
handler is causing a conflict of some kind. Just guessing.

*** Bug 91212 has been marked as a duplicate of this bug. ***
this happens on linux too
OS: Windows 2000 → All
i'm having a bad side effect of loading testcase - context menu stopped working.
 no reaction on right clicks.. keyboard shortcuts like CTRL-N stopped working too.

sorry - linux 2001072521 nightly build.
Target Milestone: --- → mozilla0.9.4
Target Milestone: mozilla0.9.4 → mozilla0.9.5
I get this on linux 2001090308. The cursor in the second window blinks really
fast and the throbber keeps on throbbin.
Blocks: 99194
Dan/Peter - Status please (nsbranch+)?
*** Bug 99333 has been marked as a duplicate of this bug. ***
Keywords: nsbranch-
status: second on my list of current nasty bugs. targetted for 0.9.5.

This seems to be a lot worse in the 20010913 Windows builds
removed keyword nsbranch since bug now has nsbranch-, per pdt mtg.
Keywords: nsbranch
*** Bug 102486 has been marked as a duplicate of this bug. ***
Target Milestone: mozilla0.9.5 → mozilla0.9.6
*** Bug 96360 has been marked as a duplicate of this bug. ***
*** Bug 104650 has been marked as a duplicate of this bug. ***
*** Bug 104820 has been marked as a duplicate of this bug. ***
I've just checked in the patch associated with bug #104769 which fixes this 
issue.

closing out as a dup...

-- rick


*** This bug has been marked as a duplicate of 104769 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified dup.  thanks for fixing this, Rick.  20011017 works like a champ on my
testcase.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: