On Mon, Oct 26, 2009 at 5:16 PM, Gabe <[email protected]> wrote: > This decision is really bothering me. Despite your claims otherwise > Browser Actions are a decidedly _not_ elegant solution. > > Consider the case that I want to build an extension that checks the > current page for a variety of different web analytics script tags > (Google analytics, Omniture, Website Optimizer, others), parse them > for useful info (acct number, check implementation errors, etc), and > if found display an icon with an optional text snippet for each.
It seems like there could be a page or browser action that says "there are some interesting analytics tags on this page", then you click that to get more information. While I agree that this makes the experience more clicks, it seems more it fits in better with Chrome's own UI. It also prevents users from getting into a situation where they have lots of buttons but only need a few of them. In any case, we are keeping an eye out for places where we don't meet the use cases and will keep them in mind when designing future UI surfaces for extensions. - 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 -~----------~----~----~----~------~----~------~--~---
