Closed
Bug 577684
Opened 15 years ago
Closed 15 years ago
Jetpack should push the JS context stack when running handlers
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | beta2+ |
People
(Reporter: benjamin, Assigned: benjamin)
References
Details
Attachments
(1 file)
|
1.86 KB,
patch
|
mrbkap
:
review+
|
Details | Diff | Splinter Review |
Jetpack message handler currently run JS from the toplevel event loop, and this breaks some assumptions in xpconnect about the JS context stack, which happens to break XHRs among other things. Pushing the saved JS context to the xpconnect stack appears to solve the issue: mrbkap, is there any other xpconnect state that I need to worry about?
|
Assignee | |
Comment 1•15 years ago
|
||
Attachment #456582 -
Flags: review?(mrbkap)
|
|
Assignee | |
Updated•15 years ago
|
blocking2.0: --- → beta2+
|
||
Updated•15 years ago
|
Attachment #456582 -
Flags: review?(mrbkap) → review+
|
|
Assignee | |
Comment 2•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•