On Wed, Jun 3, 2009 at 1:00 PM, Aaron Boodman <a...@chromium.org> wrote:
>
> [I actually created this awhile ago, but never sent it 'round]
>
> It is really common for extensions to want to offer additional
> contextual options for content elements. For example "Download this
> movie", "edit this image", "call this phone number", etc.
>
> You can use content scripts for this, but since it is such a common
> task, I think it deserves its own proper API. This would allow this
> class of extensions to interact well with pages, with each other, and
> have a nice consistent UI.
>
> Anyway, here's an API proposal for such a thing:
>
> http://dev.chromium.org/developers/design-documents/extensions/gleam-api
>
> Comments wanted!
I think this general concept would be great.
Say I have an extension that allows me to open images in Photoshop.
Does that mean all images would have these things highlighting them?
That seems like it would be annoying.
When I read this, I first thought it was just a way to insert stuff
into a context menu when the user right-clicks on that. Perhaps having
both modes would be useful. The image editing or video download
extension would register itself as interested in these things only
from the context menu, and they'd get a chance to insert commands into
that menu to do whatever they want.
This could also be useful for less-intrusive extensions. I want the
ability to right-click on one to open it in my favorite mapping
provider, but I *don't* want all addresses glowing blue.
Brett
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
