Closed Bug 4220 Opened 26 years ago Closed 25 years ago

[BLOCK] Apprunner fails to open window from JavaScript

Categories

(Core :: JavaScript Engine, defect, P1)

Product:
Core
Component:
JavaScript Engine
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: gerardok, Assigned: hyatt)

References

Details

Project: Seamonkey (apprunner) BuildId: Mar18 Platforms: WinNT/95/98, Linux No browser window is opened when window.open() is called inside a SCRIPT element. window.open() works fine on viewer.exe. This failure is happening on win32, Linux and possibly on MacOS. Steps to reproduce: 1. Create an HTML file with the following content: <HTML> <HEAD> <TITLE>test.html</TITLE> </HEAD> <BODY> <SCRIPT type="text/javascript"> window.open("http://www.netscape.com", "FooWindow"); </SCRIPT> </BODY> </HTML> 2. Load that file in apprunner Expected results: It opens a child window with Netscape homepage in it. Actual Results: No child window is opened.
Priority: P3 → P1
Setting priority to P1 since it's blocking QA automation.
Assignee: don → trudelle
Re-assigned to trudelle@netscape.com. Peter, this looks like work for Dan ...
Assignee: trudelle → danm
Summary: Apprunner fails to open window from JavaScript → [BLOCK] Apprunner fails to open window from JavaScript
Target Milestone: M4
reassigning to danm as p1 for m4, adding BLOCK to summary since it is holding up QA automation.
*** Bug 2580 has been marked as a duplicate of this bug. ***
*** Bug 869 has been marked as a duplicate of this bug. ***
Status: NEW → ASSIGNED
Target Milestone: M4 → M5
Moving to M5 just because there's no time for me to address this in M4. PS: this is a blocker for automation testing because none of the JavaScript window.xxx() functions work with AppRunner windows. Windows can be opened using the ToolkitCore, but those windows don't play well with most of the JavaScript properties and methods. Could be ugly. Not sure I want this one, but I might, since Viewer's lack of a problem here implies it may not be a JavaScript issue. I'll investigate.
Component: Apprunner → JavaScript
QA Contact: 3853 → 4015
There's a couple of problems here. One of them is the security issue involved in separating a webshell from the containing XUL. Resolution isn't trivial: some rethinking is wanted.
Assignee: danm → hyatt
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
I'm close to a halfway fix for this. I can probably get the window up and loading the URL, but I won't have window.open returning a valid return value, i.e., by M5, don't write code like var newWindow = window.open("http://home.netscape.com/", "MyFooWindow"); I can make the call open the window and load the URL, but I don't think I can give you a valid handle to the window by M5. Is this acceptable, gerardo?
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
This is now fixed. There will undoubtedly be additional bugs related to window.open(), so file them as you discover them.
Status: RESOLVED → REOPENED
Re-tested on Apprunner 0422 build, and a second attempt to open a new window is failing on any platform. Now Apprunner opens a new window but it crashes the second time a new window is opened; i.e. by loading again the same page in the parent window. Bug reopened. It might not be quite the same failure as bug 5490. Please see also bug 5443 for related failure on viewer.exe. I think we can avoid using window handlers, so the current solution would be acceptable.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Closing back out. This problem you're reporting is the same problem described in Bug 5490. This problem doesn't just apply to window.open.
Status: RESOLVED → VERIFIED
Verified on 0429 build.
Changing component to "Javascript Engine". "Javascript" component is being retired.
You need to log in before you can comment on or make changes to this bug.