Closed Bug 267952 Opened 20 years ago Closed 15 years ago

###!!! ASSERTION: chrome shouldn't be calling alert(), use the prompt service: 'Error', file r:/mozilla/dom/src/base/nsGlobalWindow.cpp, line 2333

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: timeless, Assigned: jag+mozilla)

References

()

Details

(Keywords: assertion)

###!!! ASSERTION: chrome shouldn't be calling alert(), use the prompt service:
'Error', file r:/mozilla/dom/src/base/nsGlobalWindow.cpp, line 2333
Break: at file r:/mozilla/dom/src/base/nsGlobalWindow.cpp, line 2333

+	filename	0x028f3ad5 "chrome://navigator/content/navigator.js"	const char *
	lineno	452	unsigned int

The alert says "Error launching browser window:no XBL binding for browser"
Product: Core → Mozilla Application Suite
related to bug 105596 ?
baffclan@yahoo.co.jp: no.
the concern here is the code that actually tosses up the dialog, not the problem
that leads the code to decide to toss up the dialog.
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.