This has come up several times.

What I am leaning toward is providing a way for users to turn off
browser actions if they don't want to see them. That way there is a
consistent UI for all extensions.

What do you all think? Would there still be a use case for an
extension turning on and off its own browser action in that case?

- a

On Fri, Dec 11, 2009 at 1:32 PM, Tim Ker <[email protected]> wrote:
> I would like to be able to be able to turn browser actions on and off
> via code as well. As there can be many ways to interact with an
> extension... and some users don't always want a browser action
> cluttering up the google chrome toolbar.... and others do :)
>
> Perhaps on the initial loading of an extension event would be good to
> hook up to.
>
> On Dec 8, 9:33 pm, Anand Rangarajan <[email protected]> wrote:
>> Hi Aaron,
>>
>> That sounds reasonable, if there is a way to pack a set of related
>> extensions. The issue is just
>> that many people may want to install multiple ones in one fell swoop. One
>> option is to just be
>> able to have a phantom extension linking to a bunch of related extensions.
>>
>> In the case of Gmail, the checker, mailto converter and Send with Gmail will
>> all be bundled.
>>
>> thanks,
>> anand
>>
>>
>>
>> On Tue, Dec 8, 2009 at 1:40 PM, Aaron Boodman <[email protected]> wrote:
>> > On Tue, Dec 8, 2009 at 1:33 PM, Anand Rangarajan <[email protected]> wrote:
>> > > Yeah, I know it can be done with pageAction, but this functionality is a
>> > > browserAction because that is
>> > > the best to provide the functionality on any page. Specifically, this
>> > > browserAction is to be able to email
>> > > the current URL and title from any page to a set of people. It solves the
>> > > common use case of unneeded
>> > > drudgery to open a tab, go to gmail, copy and paste the URL to send to
>> > some
>> > > people.
>> > > But, there is also a content script with this extension which converts
>> > > mailtos to gmail compose URLs.
>> > > I want to provide an option to turn off the browserAction since some
>> > people
>> > > do not seem to want the
>> > > button in their real estate.
>> > > I am guessing the answer to this is that it is not possible right now
>> > > without actually dropping the icon
>> > > in the manifest itself.
>>
>> > I suggest just having two extensions. These are really two separate
>> > features, and the Chrome extensions model is 1 feature per-extension.
>>
>> > - a
>
> --
>
> You received this message because you are subscribed to the Google Groups 
> "Chromium-extensions" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/chromium-extensions?hl=en.
>
>
>

--

You received this message because you are subscribed to the Google Groups 
"Chromium-extensions" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/chromium-extensions?hl=en.


Reply via email to