Closed Bug 73893 Opened 24 years ago Closed 23 years ago

Failure to open a child window results in persistent phantom window

Categories

(Core :: Networking, defect)

PowerPC
Mac System 9.x
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 37743
mozilla0.9.4

People

(Reporter: tarahim, Assigned: danm.moz)

References

()

Details

2001032808 trunk. Goto URL. Click "View Results" in the Quick Vote at the middle of the page. Quite frequently, no new window pops up even though a new window title "Mozilla" is added under the Task menu. At that point, you can not quit Mozilla. Closing all the window do not help.
I think this is not a networking bug. Could be the JSProtocolhandler. Reassigning to jst for now. Please reassign as necessary.
Assignee: neeti → jst
Window problem, not JS protocol handler. Over to danm.
Assignee: jst → danm
I think one way to fix this is to draw a child window immediately after the JS calls it rather than after some networking. There was a similar problem where a target window did not get focus until its content was downloaded.(fixed bug 70682)
This bug also happens when Add Bookmark dialog fails to open when there is a problem with Bookmarks.html file (bug 74969).
https://www.paypal.com/cgi-bin/webscr?amount=20.00&return=http%3A//www.christopherlydon.org&item_name=My+Contribution&submit.x=36&submit.y=17&business=jake%40christopherlydon.org&item_number=001&undefined_quantity=1&cmd=_xclick is another page with JS openWindow(url) that fails a lot. If CNN.com responds too well to repoduce this bug, try this Paypal site. There are several question mark icons and the Term of Use link that are supposed to call openWindow.
I think the failure of opening JS coded popups have gotten worse in recent builds. Reappearance of bug 32269 may have something in common with this failure.
Target Milestone: --- → mozilla0.9.2
mass move, v2. qa to me.
QA Contact: tever → benc
Assuming you're only prevented from quitting, this no longer fits the profile for the current release cycle, ->0.9.3
Target Milestone: mozilla0.9.2 → mozilla0.9.3
The inevitable force quitting is tricky. Sometimes, it brings down networking altogether and makes it necessary to reboot the computer. BTW, This problem at www.cnn.com has gotten seriously worse in 2001060114 trunk build.
The URL is WFM in 2001062914. However, there are some seemingly random instances where target window fails to open, which prevents Mozilla from quitting. Currently, this renders the network socket unavailable for entire system and makes it necessary to reboot the machine. The failure of opening target windows seems to be aggravated by tight memory condition.
can we update the component?
Please do as appropriate.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
I can't reproduce this. Ten times opening the poll results window on CNN; no problems. The paypal site doesn't try to open a window in Mozilla or Navigator 4. Can you give a specific bookmarks.html error that will cause this problem? (PS: could this be the same as bug 37743 ?)
Ah, yes. I could not find it when I queried Bugzilla. duping this to bug 37743. BTW, there is no specific URL that can be given, because there are a lot of instances to cause this. Currently, setting cache size to abnormally small can cause this to happen. *** This bug has been marked as a duplicate of 37743 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.