267580 - chrome://global/content/nsHelperAppDlg.xul, line 0: uncaught exception: [nsIDOMWindowInternal.outerWidth]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/bindings/dialog.xml :: centerWindowOnScreen :: line 10...

Status: NEW

(Core :: XUL, defect, P5)

Description

[timeless]

WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(treeOwnerAsWin->GetSize(aOuterWidth,
&notused))) failed, file r:/mozilla/dom/src/base/nsGlobalWindow.cpp, line 1679
JavaScript error: chrome://global/content/nsHelperAppDlg.xul, line 0: uncaught
exception: [Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIDOMWindowInternal.outerWidth]"  nsresult: "0x80004005
(NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://global/content/bindings/dialog.xml :: centerWindowOnScreen :: line 103"
 data: no]

i got this while using winEmbed, this happens before i completed all the steps
that it took to trigger bug 267579.

i'm not sure what to fix, we could fix the xbl (dialog.xml), the caller
(nsHelperAppDlg.xul), or whatever it was that caused
nsIDOMWindowInternal.outerWidth to throw failure

Comment 1

[[e-mail]]

Well, window.outerWidth fails in winEmbed; is it documented to?

Comment 2

[timeless]

documentation? what's that?

Comment 3

[[e-mail]]

(In reply to comment #2)
>documentation? what's that?
Something that stops the bug getting resolved invalid?

Comment 4

[timeless]

The original summary for this bug was longer than 255 characters, and so it was truncated when Bugzilla was upgraded. The original summary was:

chrome://global/content/nsHelperAppDlg.xul, line 0: uncaught exception: [nsIDOMWindowInternal.outerWidth]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://global/content/bindings/dialog.xml :: centerWindowOnScreen :: line 103"  data: no]