Closed
Bug 11404
Opened 25 years ago
Closed 25 years ago
window.open doesn't show the specified page
Categories
(Core :: DOM: Core & HTML, defect, P1)
Core
DOM: Core & HTML
Tracking
()
VERIFIED
FIXED
M9
People
(Reporter: gerardok, Assigned: danm.moz)
References
Details
(Whiteboard: [QA M9 BLOCKER] fix in hand)
Attachments
(1 file)
|
192 bytes,
text/html
|
Details |
Overview Description:
When a window is opened using JavaScript, the page specified in window.open is
loaded but Apprunner loads the home page right after that. The home page stays
on screen instead of the specified page.
Steps to Reproduce:
1) Create an HTML file with the following content, or load the above attachment:
<HTML>
<HEAD>
<TITLE>test.html</TITLE>
</HEAD>
<BODY>
<SCRIPT type="text/javascript">
window.open("http://bubblegum", "ChildWindow");
</SCRIPT>
</BODY>
</HTML>
Actual Results: Home page at mozillazine.org displayed in new window.
Expected Results: New window opened and showing the bubblegum server home page.
Build ID & Platform Bug Found: 1999-08-06-09-M9 on Win NT
Additional Builds and Platforms Tested On: 1999-08-04-M9 on MacOS
Additional Information: Mac doesn't even open a new window.
|
||
Updated•25 years ago
|
Assignee: vidur → joki
|
|
||
Comment 3•25 years ago
|
||
Joki owns window.open() and danm has been making many changes. If I keep getting bugs on this front, I'm going to ask to review all changes made to window.open(). :-(
I don't think this is a problem with window.open: the bug doesn't occur if you remove the "browser.startup.homepage" preference from all.js. Seems like it's just a case of the treatment of the homepage preference being too forceful. Give this one to me, Tom, if you don't want it.
This failure happens only if the opened page contains frames. If there are no frames, the page loads properly.
|
||
Comment 6•25 years ago
|
||
That's no entirely true. http://warp is a frameset page and it loads fine.
|
||
Updated•25 years ago
|
Assignee: joki → danm
|
|
||
Comment 7•25 years ago
|
||
joki tells me materfull dan is back on this
Status: NEW → ASSIGNED
Whiteboard: [QA M9 BLOCKER] → [QA M9 BLOCKER] fix in hand
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
This bug is a timing dependent thing, and isn't reliably reproducible on my machine.
After coding a fix, I can't see the problem with the fix enabled or disabled. So I believe
the problem has been fixed by disabling the browser appcore's automatic loading of the
default page for windows opened from JavaScript, but since I can't reproduce the problem
today, I can't be certain.
Note that, while following the bug reproduction steps faithfully, the second ("bubblegum")
window loads the correct page, rather than mozillazine (or whatever was specified in your
preferences), the location bar still reads "about:blank". That's a different bug which I can
also fix, but am holding off on during the current stability phase.
Calling it fixed, with caveat mentioned above.
You need to log in
before you can comment on or make changes to this bug.
Description
•