Open Bug 1185785 (webext-android) Opened 5 years ago Updated 2 months ago

[tracking] Extension API for Android

Categories

(WebExtensions :: Android, defect, P3)

34 Branch
defect

Tracking

(relnote-firefox 48+)

Tracking Status
relnote-firefox --- 48+

People

(Reporter: billm, Unassigned)

References

(Depends on 6 open bugs)

Details

(Keywords: meta, Whiteboard: triaged, [geckoview])

Filing this to track progress on making the extension API in bug 1175770 work in Fennec.
Priority: -- → P2
Component: Extension Compatibility → WebExtensions
Product: Firefox → Toolkit
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.
Summary: Extension API for Android → [tracking] Extension API for Android
Blocks: webext
Depends on: 1203233
Flags: blocking-webextensions+
Whiteboard: triaged
Duplicate of this bug: 1208028
Depends on: 1251042
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-
Assignee: nobody → mwein
Depends on: 1119890
Depends on: 1258975
Depends on: 1260245
No longer depends on: 1258975
Alias: webext-android
Depends on: 1260548
Depends on: 1260888
Depends on: 1261253
Depends on: 1263005
Depends on: 1269062
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)
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)
No longer depends on: 1119890
Adding Arcadio, who is working to tie together WebExtensions messaging for 48.
Flags: needinfo?(atsay)
Assignee: mwein → nobody
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.
No longer blocks: webextensions-chrome-gaps
Depends on: 1260916
Depends on: 1300808
Component: WebExtensions: Untriaged → WebExtensions: Android
Flags: blocking-webextensions-
Keywords: dev-doc-needed
Depends on: 1331126
Depends on: 1331128
Depends on: 1302504
Depends on: 1316442
Using this tracking bug for the first pass at high profile extensions on Android and the first wave of Android WebExtensions.
Depends on: 1338371
Depends on: 1338381
No longer depends on: 1331126
Depends on: 1330159
Depends on: 1360448
Depends on: 1364945
Depends on: 1386316
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
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)
(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)
A release note was added I believe. At least I typed one into a google doc somewhere.
Flags: needinfo?(amckay)
Blocks: 1411651
No longer blocks: 1411651
Depends on: 1411651
Keywords: meta
Depends on: 1404014
Product: Toolkit → WebExtensions
Depends on: webext-geckoview

fennec does not depend on geckoview.

moving fennec work out of p2

No longer depends on: webext-geckoview
Priority: P2 → P3

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
Whiteboard: triaged → triaged, [geckoview]

If this is still relevant, I think it's missing the following https://bugzilla.mozilla.org/show_bug.cgi?id=1330160

You need to log in before you can comment on or make changes to this bug.