Closed
Bug 1185785
(webext-android)
Opened 9 years ago
Closed 4 years ago
[tracking] Extension API for Android
Categories
(WebExtensions :: Android, defect, P3)
Tracking
(relnote-firefox 48+)
RESOLVED
INACTIVE
Tracking | Status | |
---|---|---|
relnote-firefox | --- | 48+ |
People
(Reporter: billm, Unassigned)
References
Details
(Keywords: meta, Whiteboard: triaged, [geckoview])
Filing this to track progress on making the extension API in bug 1175770 work in Fennec.
Reporter | ||
Updated•9 years ago
|
Priority: -- → P2
Reporter | ||
Updated•9 years ago
|
Component: Extension Compatibility → WebExtensions
Product: Firefox → Toolkit
Comment 1•9 years ago
|
||
Is the plan to have day-1 feature parity with desktop Firefox?
Comment 2•9 years ago
|
||
(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.
Reporter | ||
Comment 3•9 years ago
|
||
Yes, we're probably not going to have Android support for a few releases.
Updated•9 years ago
|
Keywords: dev-doc-needed
Updated•9 years ago
|
Summary: Extension API for Android → [tracking] Extension API for Android
Updated•9 years ago
|
Flags: blocking-webextensions+
Updated•9 years ago
|
Whiteboard: triaged
Comment 5•9 years ago
|
||
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.
Flags: blocking-webextensions+ → blocking-webextensions-
Updated•9 years ago
|
Assignee: nobody → mwein
Updated•9 years ago
|
Alias: webext-android
Added to Fx48 Aurora release notes
relnote-firefox:
--- → 48+
Comment 7•8 years ago
|
||
Talking to marketing about this, how much of this work will land in 48 and depending on that, is it worth mentioning?
Flags: needinfo?(mwein)
Flags: needinfo?(amckay)
Comment 8•8 years ago
|
||
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.
Flags: needinfo?(mwein)
Flags: needinfo?(atsay)
Flags: needinfo?(amckay)
Comment 9•8 years ago
|
||
Adding Arcadio, who is working to tie together WebExtensions messaging for 48.
Flags: needinfo?(atsay)
Updated•8 years ago
|
Assignee: mwein → nobody
Comment 10•8 years ago
|
||
Why does this ticket block bug 1161828 (parity with Chrome extension API)? Chrome for Android does not support any browser extensions.
Comment 11•8 years ago
|
||
Yeah you're right, it shouldn't block Chrome Parity.
No longer blocks: webextensions-chrome-gaps
Updated•8 years ago
|
Component: WebExtensions: Untriaged → WebExtensions: Android
Flags: blocking-webextensions-
Updated•8 years ago
|
Keywords: dev-doc-needed
Comment 12•8 years ago
|
||
Using this tracking bug for the first pass at high profile extensions on Android and the first wave of Android WebExtensions.
Comment 13•7 years ago
|
||
Looks like we're shipping this to beta 56. Can you suggest a release note? Or maybe it needs developer documentation at https://developer.mozilla.org/en-US/Firefox/Releases/56.
Flags: needinfo?(whuang)
Keywords: dev-doc-needed
Comment 14•7 years ago
|
||
I had transitioned Fennec relevant tasks to 1e Wesly since July. (sorry about the names being confusing)
BTW, I thought the extension changes will be in 57, but looks like some are partially going into 56.
Flags: needinfo?(whuang) → needinfo?(wehuang)
Comment 15•7 years ago
|
||
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #13)
> Looks like we're shipping this to beta 56. Can you suggest a release note?
> Or maybe it needs developer documentation at
> https://developer.mozilla.org/en-US/Firefox/Releases/56.
Hi Andy, seems it was talked about in Firefox 48 and maybe worth mentioning again since it's riding 56? Would you help on Liz's inquiry in comment13? Thanks.
(In reply to Andy McKay [:andym] from comment #8)
> 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.
Flags: needinfo?(wehuang) → needinfo?(amckay)
Comment 16•7 years ago
|
||
A release note was added I believe. At least I typed one into a google doc somewhere.
Flags: needinfo?(amckay)
Updated•7 years ago
|
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Depends on: webext-geckoview
Comment 17•5 years ago
|
||
fennec does not depend on geckoview.
moving fennec work out of p2
No longer depends on: webext-geckoview
Priority: P2 → P3
Comment 18•5 years ago
|
||
This looks historic to me; In WebExtensions pages we don't tend to record mobile support for Extensions anyway, so I'm not really sure what would be done here.
Keywords: dev-doc-needed
Updated•5 years ago
|
Whiteboard: triaged → triaged, [geckoview]
Comment 19•5 years ago
|
||
If this is still relevant, I think it's missing the following https://bugzilla.mozilla.org/show_bug.cgi?id=1330160
Comment 20•4 years ago
|
||
We're not actively using this bug to track bugs any more.
Watch WebExtensions::Android and GeckoView::Extensions to see relevant bugs.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•