Closed Bug 543524 Opened 15 years ago Closed 15 years ago

Ensure correct onReady event behavior in all Jetpack content documents

Categories

(Add-on SDK Graveyard :: General, defect, P2)

Product:
Add-on SDK Graveyard
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: dbuchner, Assigned: avarma)

References

Details

Things to watch: - onReady events are not fired for each iframe in the content documents - Make sure onReady events are fired on each load of the window.location change - Make sure onReady events are predictable and fire in all expected circumstances For more items to watch out for, please see the attached duplicate tickets.
Assignee: nobody → avarma
These are best practices that we should make sure make it into all APIs that access such content documents. Daniel is going to add it as an implementation detail to those JEPs to which it applies.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product. To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Version: 0.1 → unspecified
You need to log in before you can comment on or make changes to this bug.