1331126 - [tracking] BrowserAction API support for Android WebExtensions

Status: RESOLVED DUPLICATE of bug 1330159

(WebExtensions :: Android, defect, P2)

Description

[Matthew Wein [:mattw]]

This bug is meant for tracking the implementation of the BrowserAction API on Fennec.

This API allows the developer to add an icon, which when clicked on can either perform an action or open up a popup. Therefore, we need help figuring out where to put this icon, as well as what to do about the browser action popup.

Comment 1

[t-v.k]

From what I can tell the PageAction API is already implemented. So I'm assuming that the only reason this hasn't been implemented yet is because no one can think of a good way of where to place the icon? 
I feel like the BrowserAction is extremely important. (Way more important than the PageAction.) I mean I've seen lots of extensions that require you to click the BrowserAction to enable/disable it and also extensions that use the popup to let the user configure the settings.  
Also, I feel like the lack of BrowserAction pushes extension developers into a corner where they start misusing the PageAction to compensate. 

And to throw some ideas for the icon placement into the room:  
 - put them below the navigation icons in the menu
 - put a general icon next to the navigation bar that toggles a popup containing all the BrowserAction icons

Comment 2

[Kris Maglione [:kmag]]

(In reply to t-v.k from comment #1)
> From what I can tell the PageAction API is already implemented. So I'm
> assuming that the only reason this hasn't been implemented yet is because no
> one can think of a good way of where to place the icon? 

No, we've already decided that these would appear in the main menu. It hasn't been implemented yet because there have been other priorities.

Comment 3

[t-v.k]

Oh alright. Where can I read up on the development?

Comment 4

[Matthew Wein [:mattw]]

Here is the best place to follow the development -- there just hasn't been much lately, but you can expect to see more updates here over the next few weeks.

Comment 5

[Matthew Wein [:mattw]]

Setting this bug to "Unassigned" since it's a tracker.

Comment 6

[Matthew Wein [:mattw]]

Moving work on this bug to bug 1330159.