| Issue 24473: | max 1 UI surface per-extension | |
| 5 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
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 action. 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 09, 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
Owner: fin...@chromium.org |
|||||||||||||||||||||||
,
Oct 16, 2009
(No comment was entered for this change.)
Status: Fixed
|
|||||||||||||||||||||||
,
Oct 16, 2009
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=29284
------------------------------------------------------------------------
r29284 | finnur@chromium.org | 2009-10-16 08:56:01 -0700 (Fri, 16 Oct 2009) | 6 lines
Changed paths:
M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension.cc?r1=29284&r2=29283
M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_constants.cc?r1=29284&r2=29283
M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_constants.h?r1=29284&r2=29283
M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_unittest.cc?r1=29284&r2=29283
Limit extensions to 1 UI surface (either Page/Browser action, but not both).
BUG=24473
TEST=Tested using unit test.
Review URL: http://codereview.chromium.org/271117
------------------------------------------------------------------------
|
|||||||||||||||||||||||
,
Oct 22, 2009
I think it's a bad idea. Let me give as an example TPGoogleReader (http://code.google.com/p/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 (http://code.google.com/p/chromium/issues/detail? 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 ( http://groups.google.com/group/chromium- extensions/browse_thread/thread/e5d09ee9c02d0c0d ) |
|||||||||||||||||||||||
,
Mar 03 (6 days ago)
(No comment was entered for this change.)
Labels: Feature-Extensions
|
|||||||||||||||||||||||
| ► Sign in to add a comment | |||||||||||||||||||||||