549319 - Ability for Jetpacks to use registered custom URLs

Status: RESOLVED INVALID

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

Description

[Daniel Buchner [:dbuc]]

Atul is point on this JEP implementation, further details here: https://wiki.mozilla.org/Labs/Jetpack/Reboot/JEP/106

Comment 1

[Atul Varma [:atul]]

Renamed 'chrome' to 'custom' in the bug summary, to avoid confusion w/ the actual chrome: scheme.

Comment 2

[Atul Varma [:atul]]

It was decided at yesterday's Jetpack meeting that this bug was a bit vague in its requirements--different contexts demand Jetpack URLs for different purposes. Sometimes a URL to a Jetpack resource needs to be unforgeable, and sometimes it doesn't; sometimes the nsIPrincipal that owns a channel to a Jetpack URL needs to be well-defined and sometimes it doesn't, which gets into the issue of JEP 115 [1]. So this bug may be marked as invalid soon and split up into different bugs that are more specific.

[1] https://wiki.mozilla.org/Labs/Jetpack/Reboot/JEP/115

Comment 3

[Atul Varma [:atul]]

Brian, any suggestion what we should do with this bug? Should we mark it invalid and have it superseded by more specific bugs?

Comment 4

[Atul Varma [:atul]]

Note that bug 553020 is one example of a more specific bug that already exists.

Comment 5

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

Resolving invalid per Atul's suggestion, but please reopen if you disagree for good reason.

Comment 6

[Dietrich Ayala (:dietrich)]

Some JEPs were still listing this as a dependency. I updated the JEP page to reflect the canceled status, pointing to this bug for explanation.

Comment 7

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