On Thu, Aug 20, 2015 at 3:32 PM, <[email protected]> wrote: > > I'm wondering if I'm doing my addon migration the right way, > I had updated manifest files according to the mopad: > https://etherpad.mozilla.org/converting-fxos-addons > But is that all? > Do we need to change the API usage like what we did to listen to addon > state change? >
AFAIK, all the old API usage should work just like before, but Fabrice would know better. If something stopped working please let us know and file a bug. > > Another thing is, how do we test our converted addons? > I tried using WebIDE in Firefox Nightly, but it seems it still looking for > manifest.webapp, > I put a fake manifest.webapp and install it in my flame with latest daily > build flashed, > and it seems that enabling the addon takes no effect. > Do we need to wait for next Aries OTA to test them? > You will need to install a build which includes bug 1191619. Also, the manifest.webapp naming on webIDE is unfortunate. Can you file a bug to allow it to also recognize update.webapp? > And since we're using manifest format like chrome, > do we still support registering activity filters (see below) in addons? > https://github.com/yzen/fxos-user-hub/blob/master/manifest.webapp#L20-L28 Good question! Again Fabrice would know better here, but most of the underpinnings for the new add-ons is the same as old add-ons. So hopefully it will just work™. If now, let's file a bug and fix it quick.
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
