New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 23879 link

Starred by 9 users

Issue metadata

Status: Fixed
User never visited
Closed: Oct 2009
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug

  • Only users with EditIssue permission may comment.

Sign in to add a comment

Finalize browser actions API

Project Member Reported by, Oct 5 2009

Issue description

They should both have the API documented at, except the page 
actions API should have an additional show(int tabID) method, and should 
not have the badge related methods.

We need to keep the current page action API for compat. This should be easy 
to do in extension_process_bindings.js.

I'm currently thinking that we should allow multiple browser actions and 
page actions per extension.

My reasoning is that although it would be neat to have one-extension one-
feature, we cannot come up with any way to do this and allow extensions to 
communicate easily. Also, it would increase memory bloat (more processes).

Comment 1 by, Oct 5 2009

Labels: Mstone-4
Just as an FYI: Having multiple Browser Actions per extension means implementing 
something similar to Page Actions, where the Chrome support js makes a native call into 
Chrome to find out what Browser Actions the extension supports and sets up events for 
each one.

Comment 3 by, Oct 5 2009

Yeah, I figure it should be pretty easy to combine the best parts of both these APIs (?
Sure. I have no problem with that.

Comment 5 by, Oct 5 2009

Labels: Pri-2

Comment 6 by, Oct 6 2009

Labels: -Pri-2 Pri-1
Bumping to P1 as it is a large API change.

Comment 7 by, Oct 10 2009

I've put a draft of how to do this here:

Please let me know what you think.

Comment 8 by, Oct 10 2009

Good stuff.

Out of curiosity... in what scenario does it make sense to update the browser action 
tooltip per tab? 

I presume details of dragging etc. apply to Browser Actions also, even though they are 
only specified for Page Actions?

nit: the documentation for setBadgeText should appear before setBadgeBackgroundColor 
and setBadgeTextColor. It would give the two latter functions more context.


Comment 9 by, Oct 10 2009

To be honest, I think the tooltip component is pretty uninteresting. I include it 
mainly for consistency with other things in the toolbar that also have tooltips.

But playing along, say you had a 'bookmark in delicious' browser action. If a tab is 
already bookmarked you might want to change the icon, and change the tooltip to say 
'edit bookmark'.

Comment 10 by, Oct 12 2009

Status: Assigned
Summary: Finalize browser actions API
Splitting into two bugs: one for browser actions and one for page actions.
The following revision refers to this bug: 

r29068 | | 2009-10-14 17:02:24 -0700 (Wed, 14 Oct 2009) | 6 lines
Changed paths:

Update browser actions api to be like new design doc.

BUG= 23879 
TEST=Install sample gmail browser action sample.

Review URL:

Comment 12 by, Oct 15 2009

Status: Fixed
Labels: Area-Internals Internals-Install
Labels: -Area-Internals -Internals-Install
Fixing a bulk edit. Looks like the search query was not correct.
Labels: Feature-Extensions
Project Member

Comment 16 by, Oct 12 2012

Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member

Comment 17 by, Mar 10 2013

Labels: -Mstone-4 -Feature-Extensions M-4 Cr-Platform-Extensions
Project Member

Comment 18 by, Mar 13 2013

Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue

Sign in to add a comment