142555 - early cross window javascript function calls fail

Status: RESOLVED INVALID

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

Description

[Stefan Praszalowicz]

When you create a new window (using window.open) and call a
javascript function defined in that window, the call fails
and the javascript console reports 'is not a function'.

The same function call done after the window is initialised and
completely drawn works ok.

It looks like the window.open function returns too quickly, before the new
window is ready.


Tested on 1.0 RC1 and latest nightly build (2002041711??)

Related ?
I've looked for that on bugzilla, it looks like people have reported the same
kind of problems for javascript to java (actually plugins in general).
See bug #106253

Comment 1

[Stefan Praszalowicz]

Attachment: Test case (part 1, needs test_popup.html)

Comment 2

[Stefan Praszalowicz]

Attachment: Test case (part 2)

Comment 3

[Phil Schwartau]

Browser, not engine --> DOM Level 0.

jst: is this a duplicate of bug 52238,  "window handle returned by 
open/openDialog does not provide a handle to a valid js context" ? 

(marked INVALID)

Comment 4

[Stefan Praszalowicz]

Hmm
I've had a look at bug 52238

It looks like the same bug.
The thing that bothers me is that the javascript function (or in case of bug
52238, the variable) is really defined, or will be (some milliseconds after the
call).

So how do you know when it's ok to call stuff on the new window ?

The fact that it's really a pain to do in javascript (no threads, no sleep, ...)
makes me think that it would be ok to handle it in the browser, just by
returning from window.open when the new window is done loading - for example
around the time onLoad is executed; or even by adding a small tempo

I realize it can be an endless thin - what about variables defined later etc..
but at least 'static' code defined right in <script> tags should be available by
the time window.open returns


No ?

Comment 5

[Mihail Daskalov]

is this related to bug 159424?

Comment 6

[Peter Van der Beken [:peterv]]

No, not related to bug 159424.

Comment 7

[Johnny Stenback (:jst)]

Mass-reassigning bugs to [e-mail]

Comment 8

[Tony Daniel]

This _might_ be the same regression I saw from 1.6 to 1.7beta where window.open
fails on a onMouseDown in the following page:

  http://www.newseum.org/todaysfrontpages/

Quick test: click on one of the front page thumbnails in the array; you should
see a new window pop up of the chosen front page image.  I don't.  Javascript
was enabled for Navigator, scripts were allowed to do everything, even the new
"Disable or replace context menus" option.  My 1.6 settings were different for
the "allow scripts" options, but my original 1.6 settings failed too, which is
why I tested with all settings checked.

Unlike the earlier comments, the Javascript console does _not_ report the
failure.  Also unlike original bug, this was on Windows XP.

Comment 9

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.

Comment 10

[Anne (:annevk)]

This is not how window.open() works. The initial document it creates is about:blank and that won't have the functions. You'll have to wait for the specified document to be loaded.