543533 - tracking bug for JS library compatibility issues

Status: RESOLVED INVALID

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

Description

[Daniel Buchner [:dbuc]]

All libraries have issues with existence inside of Jetpack's js sandbox (mostly due to their reliance on a traditional DOM).  Let's offer relays and fixes where possible and where difficulty overrides gain, publish a doc that outlines what to wath out for and how to bring js libs into compatibility with Jetpack

Comment 4

[Myk Melez [:myk] [@mykmelez]]

This seems pretty useful, although the bug description is a bit vague.  Is there a specific thing that needs to be done here (perhaps just to write a specification of the things Javascript libraries would need to do in order to be compatible with Jetpack?).

Also, tentatively scheduling this for 0.2, as it seems to be the kind of thing that developers will want early in order to be productive.  Atul: do you think you will have time over the next month to address whatever needs to be addressed here?

Comment 5

[Atul Varma [:atul]]

I think I'll be able to address some of it, but I'm not sure what all is actually encompassed by "js libraries".  I know what would be involved in making most of jQuery work, for instance, because I know what jQuery does; but I'm not very familiar with other libraries like Dojo, MooTools, and so forth, so the scope here feels a bit vague.

Comment 6

[Myk Melez [:myk] [@mykmelez]]

We'd like to ensure that you can use JavaScript libraries with the Jetpack SDK, so we should resolve any issues in the SDK that prevent that from happening. At the same time, those issues should be filed as specific individual bugs.  This one might be useful as a tracking bug for those issues, however, so morphing it accordingly.

Note: it's also possible that the page workers implementation (bug 546740) will make this unnecessary, as you'll be able to use JavaScript libraries in those pages, and that'll be sufficient.  If so, we can close this bug then.  Leaving it open for now, though (but without a priority and target milestone, as it's not clear by when we should fix this).

Comment 7

[Myk Melez [:myk] [@mykmelez]]

We haven't yet had individual bugs filed for this one to track, so this bug doesn't seem to be necessary.

When you notice issues with Jetpack compatibility with JS libraries in the future, please do file individual bugs on each discrete issue, and we'll track them individually.

Comment 8

[Myk Melez [:myk] [@mykmelez]]

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".