Using Browser Action as a general action and Page Action as a page specific action are the purposes of these two features, I believe. Merging the two into one (be it Browser Action or Page Action) kind of loses the intended purpose. However, having multiple (two, actually - one and one, but not more than one) user interface surfaces for really related actions - seem appropriate in cases such as this (and I am sure there are more).
Maybe you could add a review for extensions that use a Browser Action and a Page Action altogether, like you have for "file://*/" permissions and NPAPI. If you see that these are not really 'two features', but one feature that simply has a general manner and a page specific manner, approve them. ☆PhistucK On Thu, Jan 21, 2010 at 15:14, Brian Kennish <bkenn...@chromium.org> wrote: > On Thu, Jan 21, 2010 at 12:03 AM, PhistucK <phist...@gmail.com> wrote: > > Regarding the suggestion in the bug - > > Adding a menu in the popup makes the extension less simple. It requires > one > > extra click (at least), which is a worse user experience than a single > click > > in the right location (browser or page action). > > True (although the other possibility I mentioned -- adding a selective > subscription link -- would only require the extra click for > subscribing not for viewing recent items), but the larger question is: > is having a few extensions that require an extra click a worse user > experience than having many extensions that unnecessarily use multiple > UI surfaces? >--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To post to this group, send email to chromium-extensi...@googlegroups.com.
To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
