Bug 567642 made it possible for code to access the harness service using the JID whether it is bundled or being run via the |cfx run| command, but it still can't necessarily access the harness service using |cfx test|, because the contract ID of the harness service is hardcoded for that command. We should fix that. In bug 567642, comment 13, referring to that bug's fix for |cfx run|, Nickolay points out: > The fix similar to above for 'test' would sprinkle 'id' properties over all > package.json files, even those that are module-packages, not program-packages. > >Perhaps we should generate the ID only if there's an invalid ID field or the >user's running 'cfx xpi' (and maybe 'cfx run', not sure)? If there's no ID, >default to a constant in the harness contract ID."
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
This doesn't seem to have mattered; let's reopen/refile if necessary in the future.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Priority: -- → P3
Resolution: --- → WONTFIX
Target Milestone: --- → Future
This was actually fixed for cases I cared about in bug 626059 -- if you specify an id in package.json, you can use it to get the harness service.
You need to log in before you can comment on or make changes to this bug.