Closed
Bug 496253
Opened 17 years ago
Closed 17 years ago
jQuery callbacks and XHRs need to be detached/aborted when a jetpack unloads
Categories
(Mozilla Labs :: Jetpack Prototype, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
0.5
People
(Reporter: avarma, Assigned: avarma)
Details
Attachments
(1 file)
|
1.59 KB,
text/plain
|
Details |
Currently, jQuery is a global singleton loaded into the about:jetpack page, so if a jetpack attaches an event handler to something or issues an XHR, it'll still be active even when the jetpack has been unloaded.
We need to either have jQuery track things on a per-jetpack basis or have jQuery loaded separately into each jetpack, so that an individual jetpack's callbacks go away when the jetpack is unloaded.
| Assignee | ||
Comment 1•17 years ago
|
||
| Assignee | ||
Updated•17 years ago
|
Attachment #381564 -
Attachment mime type: text/html → text/plain
Updated•17 years ago
|
Assignee: nobody → avarma
Priority: -- → P2
Target Milestone: -- → 0.5
| Assignee | ||
Comment 2•17 years ago
|
||
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•