My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 24473: max 1 UI surface per-extension
7 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Closed:  Oct 2009

  • Only users with EditIssue permission may comment.

Sign in to add a comment
Project Member Reported by, Oct 9, 2009
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.
Oct 9, 2009
Please see related API proposal in  bug 23879 .
Oct 12, 2009
(No comment was entered for this change.)
Labels: Pri-1
Oct 15, 2009
(No comment was entered for this change.)
Status: Started
Oct 16, 2009
(No comment was entered for this change.)
Status: Fixed
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).

TEST=Tested using unit test.

Review URL:

Oct 22, 2009
#6 tpreal
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.
Jan 20, 2010
 Issue 32614  has been merged into this issue.
Jan 21, 2010
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 )
Mar 3, 2010
(No comment was entered for this change.)
Labels: Feature-Extensions
Oct 12, 2012
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.
Labels: Restrict-AddIssueComment-Commit
Mar 10, 2013
(No comment was entered for this change.)
Labels: -Mstone-4 -Feature-Extensions M-4 Cr-Platform-Extensions
Mar 13, 2013
(No comment was entered for this change.)
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Sign in to add a comment

Powered by Google Project Hosting