Closed
Bug 476771
Opened 16 years ago
Closed 16 years ago
Various events should be asynchronous
Categories
(Core :: Audio/Video, defect)
Core
Audio/Video
Tracking
()
RESOLVED
FIXED
People
(Reporter: roc, Assigned: roc)
References
Details
(Keywords: fixed1.9.1)
Attachments
(1 file)
|
1.49 KB,
patch
|
cajbir
:
review+
roc
:
approval1.9.1+
|
Details | Diff | Splinter Review |
According to the spec, events like "load", "ended" and the "emptied" and "error" events fired by NetworkError should fire asynchronously, and it's definitely safer for us if we do that.
Attachment #360426 -
Flags: review?(chris.double)
Flags: wanted1.9.1+
|
||
Updated•16 years ago
|
Attachment #360426 -
Flags: review?(chris.double) → review+
|
Assignee | |
Comment 1•16 years ago
|
||
Oops. this bug shouldn't be about canceling events at the right times, we need to do that separately, probably when we rework the load algorithm again.
Summary: Various events should be asynchronous, and cancelled at the right times → Various events should be asynchronous
|
|
Assignee | |
Updated•16 years ago
|
Attachment #360426 -
Flags: approval1.9.1+
|
|
Assignee | |
Updated•16 years ago
|
Whiteboard: [needs landing]
|
|
Assignee | |
Comment 2•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: [needs landing] → [needs 191 landing]
Version: 1.9.0 Branch → Trunk
|
|
Assignee | |
Comment 3•16 years ago
|
||
Keywords: fixed1.9.1
Whiteboard: [needs 191 landing]
You need to log in
before you can comment on or make changes to this bug.
Description
•