Filing this to track progress on making the extension API in bug 1175770 work in Fennec.
Is the plan to have day-1 feature parity with desktop Firefox?
(In reply to 4mr.minj from comment #1) > Is the plan to have day-1 feature parity with desktop Firefox? No. There's an early release riding the trains for Firefox 42 on Desktop; there's nothing likely to hit Fennec until at least Fennec 44. billm or margaret or mfinkle may have color to add here.
Yes, we're probably not going to have Android support for a few releases.
Taking off a blocker for 1.0, we'll see if we can get the toolkit APIs and basic support working, but if we can't it won't block.
Added to Fx48 Aurora release notes
Talking to marketing about this, how much of this work will land in 48 and depending on that, is it worth mentioning?
In Firefox 48 there is support for Android in WebExtensions, enabling developers to write ONE extension for Chrome, Opera, Firefox and Firefox for Android, assuming that they stick to the APIs that Android provides (as documented on MDN). I think this is a big deal and we should talk about it a lot :) Amy is doing some co-ordination of the Firefox 48 message, so adding a need info.
Adding Arcadio, who is working to tie together WebExtensions messaging for 48.
Why does this ticket block bug 1161828 (parity with Chrome extension API)? Chrome for Android does not support any browser extensions.
Yeah you're right, it shouldn't block Chrome Parity.
Using this tracking bug for the first pass at high profile extensions on Android and the first wave of Android WebExtensions.