The default bug view has changed. See this FAQ.

test_bug296375.xul makes incorrect assumptions about the event ordering

RESOLVED FIXED in mozilla12

Status

()

Core
DOM: Events
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Ehsan, Assigned: Ehsan)

Tracking

unspecified
mozilla12
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
This test implicitly assumes that events added in order will be fired in order.  We should just call finish when we know that we're done.
(Assignee)

Comment 1

5 years ago
Created attachment 587138 [details] [diff] [review]
Patch (v1)
Assignee: nobody → ehsan
Status: NEW → ASSIGNED
Attachment #587138 - Flags: review?(bugs)
Comment on attachment 587138 [details] [diff] [review]
Patch (v1)

Does addLoadEvent not guarantee the right order? That would be bug in
mochitest. addEventListener does guarantee the order. Is mochitest not using that?

But anyway, looks ok.
Attachment #587138 - Flags: review?(bugs) → review+
(Assignee)

Comment 3

5 years ago
No, mochitest rolls its own implementation, IIRC.
(Assignee)

Comment 4

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/2b4c5610aa69
Target Milestone: --- → mozilla12
(Assignee)

Comment 5

5 years ago
https://hg.mozilla.org/mozilla-central/rev/2b4c5610aa69
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.