In bug 1366026 Screenshots is being added to a page action menu panel. This bug is to create a page action menu panel API. Perhaps its one that screenshots could use. This API would presumably of similar structure to browserAction, pageAction in that its defined in the manifest and creates on click events and maybe a popup? There isn't any UX defined for how they would appear that I'm aware of, but questions include: would they show the add-on icon, would they all be grouped in their own section, could they add anything on the right, could an add-on add any extra dynamic text, what does clicking on them do? You will likely note that I just copy and pasted some of this from bug 1366389. I'm assuming they'll be very similar.

Is the existing pageAction sufficient? https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/pageAction

Are you proposing that we change pageAction to no longer appear in the URL bar and appear in the page action menu? I've got serious concerns about that, such as: how will a user know its there? What about the other questions about where a page action menu item appears in the list of menu actions, what it settings it can set and what it can do?

examine priority once unblocked

(In reply to Andy McKay [:andym] from comment #2) > Are you proposing that we change pageAction to no longer appear in the URL > bar and appear in the page action menu? I've got serious concerns about > that, such as: how will a user know its there? This makes sense if you look at the Photon spec: https://mozilla.invisionapp.com/share/ENBBK0F9U#/screens/230998673 It allows you to pin items from the page action menu to the url bar. What I would do is either add extensions by default to the url bar, either add an animation to indicate that the add-on is inside the page action menu (eg. add-on icon bouncing on top of the page action menu).

That was my understanding as well. The same button could be moved between url bar and page action menu by the user, so it doesn't make sense for that to be a separate api. Perhaps an option to put the page action in the menu (goes to url bar by default), but other than that, there is not much we should do here IMO.

Oh I haven't seen that part of the photon mock, thanks for the heads up. If its a matter of the user choosing to move the page action into the menu, or out as appropriate then that's great. Although I bet someone will want to do as you say in comment 5 zombie and put the page action in the menu by default.