Closed Bug 360219 Opened 18 years ago Closed 16 years ago

JS with alert() aborts if a JS error happens while alert is up

Categories

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

x86
Linux
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ajschult784, Unassigned)

References

Details

(Keywords: regression, testcase)

Attachments

(1 file)

With linux seamonkey build 2006-11-09-09-trunk, if there is a script, that puts up a dialog, but a JS error happens while it's up, the first script aborts once the dialog is closed.  This can happen via an onload event fired from an image that finishes loading while the alert is up.  This is bustage from bug 326273 / bug 74331.
Attached file testcase
1. load testcase
2. get "foo" alert
3. wait for the image to load
4. Click OK
5. "bar" alert does not open
I think we should block on this, actually.  This could cause web apps to break in weird ways, I suspect.

This _is_ limited to an error in the same window (on the same JSContext), right?
Flags: blocking1.9?
Ideally we should not run scripts while modal dialogs are up. We have bugs on that currently marked as blockers. If that is fixed this will more or less go away.
This doesn't appear to be a problem in Firefox, there we don't fire the onload for the image until both alert()'s are done, no matter how long you wait. Is this a Seamonkey only problem, or did it simply get fixed at some point?
Hmm.  I'm not seeing the problem in trunk seamonkey either, come to think of it...  I'd sort of assumed it was still here.
Clearing since this doesn't seem to be a problem any more, please renominate if you can reproduce
Flags: blocking1.9?
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a5pre) Gecko/20070515 SeaMonkey/1.5a] (nightly) (W2Ksp4)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9pre) Gecko/2008060702 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4)

WorksForMe, (on Windows 2000).

Andrew,
Can you reproduce with current SeaMonkey v2.0a1pre (on Linux) ?
Blocks: 381699
this got fixed between SM builds 2007-05-04-08-trunk and 2007-05-05-09-trunk

I don't see anything in that range that looks particularly relevant, so WFM
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: