Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 7 users
Status: Fixed
Closed: Oct 2009
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Feature

  • Only users with EditIssue permission may comment.

Sign in to add a comment
max 1 UI surface per-extension
Project Member Reported by, Oct 9 2009 Back to list
For extensions beta, we want to start out limiting extensions to a maximum of 
1 UI "surface". By "surface", we mean toolstrip, browser action, or page 

UI management gets much simpler if there is a concrete relationship between 
user-visible features and extensions. And since we now have the bubble, and 
will eventually have the options UI, we think that there should be enough 
real-estate for people to do interesting things within this limitation.

At the very least, it easier to add than take away, so we would prefer to 
start with 1 and relax over time.
Comment 1 by, Oct 10 2009
Please see related API proposal in  bug 23879 .
Comment 2 by, Oct 12 2009
Labels: Pri-1
Comment 3 by, Oct 15 2009
Status: Started
Comment 4 by, Oct 16 2009
Status: Fixed
Comment 5 by, Oct 16 2009
The following revision refers to this bug: 

r29284 | | 2009-10-16 08:56:01 -0700 (Fri, 16 Oct 2009) | 6 lines
Changed paths:

Limit extensions to 1 UI surface (either Page/Browser action, but not both).

BUG= 24473 
TEST=Tested using unit test.

Review URL:

Comment 6 by, Oct 22 2009
I think it's a bad idea. Let me give as an example TPGoogleReader 
( - it has a toolstrip for reading feeds, and 
the page action for subscribing / viewing feeds. It's perfectly logical to connect 
these two things in one extension, and to put the UI elements in two different places.
 Issue 32614  has been merged into this issue.
As described in my duplicated (
id=32614), I believe it to be sensible to have various UI surface elements in certain 
cases, where page actions are literally only the page action and the browser action is 
used as a panel overview. This was also discussed on the Chromium extensions mailing 
list (
extensions/browse_thread/thread/e5d09ee9c02d0c0d )
Labels: Feature-Extensions
Project Member Comment 10 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 11 by, Mar 10 2013
Labels: -Mstone-4 -Feature-Extensions M-4 Cr-Platform-Extensions
Project Member Comment 12 by, Mar 13 2013
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Sign in to add a comment