On Mon, Oct 19, 2009 at 10:05 AM, Robert Billingslea <[email protected]> wrote: > Thanks Eric, > > I am a member of LastPass, so an example of clipboard usage would be to copy > newly generated passwords. > > > I had considered all of these options for mole replacements, but I can see > some drawbacks with all of them: > > 1) animated icon is far too easy for the avg user to miss (in my opinion) > and doesn't allow easy distinctions between disparate events w/o the need > for the user to click (We are currently using moles as a notification bar > replacement until APIs are added) > > 2) writing a div in the content script has 2 issues for us: > a) Depending on what is in this window, it poses a potential security > risk. This data is available to javascript on the page. > b) complicated because it inherits the css of the page. Not a showstopper, > but requires us to be meticulous in assigning styles to every element or it > can be rendered differently depending on the page. > > 3) Most of what we are doing is pertinent to the current page (eg, giving an > option what login or form fill profile to choose, so it doesn't make sense > to be on a new page). > > I think exposing an API to simply open the browser action popup (very > similar to how moles work) would fix it for us.
I agree with your assessment of the various options. I don't think we're going to consider opening the browser action popup without the user clicking on it at this point, but I'll bounce it off of the rest of the team. In the meantime, given your constraints, I'll go back to recommending option #1 for now. While I agree it's not as noticeable, I think it's the best tradeoff in the short term. In the longer term (post our initial public launch of the extension API), we're looking to add some more specific APIs that are probably closer to what you need. One is the ability to add an infobar to the page: http://code.google.com/p/chromium/wiki/InfoBarExtensionAPI It looks like this is the style of UI that you use for Firefox, so hopefully this is in line with what you need. Erik > > Thanks for the consideration, > Bob > > > On Mon, Oct 19, 2009 at 12:12 PM, Erik Kay <[email protected]> wrote: >> >> On Sun, Oct 18, 2009 at 12:32 PM, Robert Billingslea >> <[email protected]> wrote: >> > We implemented our extension using the toolstrip and moles and now are >> > looking to replace it with browser actions. >> > I haven't come across any APIs for mole replacement >> > (specifically chrome.toolstrip.expand), are they currently available or >> > still in the works? (We need to pop the overlay not just when a user >> > clicks >> > on the button, but also when events occur in the content script). >> >> Hi Robert. There's no direct replacement for what you're looking to >> do. Here are a few alternatives though: >> - Rather than causing a popup automatically, instead animate a browser >> action icon with some status and let the user click on it to see the >> popup. >> - Do the popup as an overlay in the page (since you've already got a >> content script there). >> - Create a new window when you need a popup (window.open()) >> >> >> > A second (unrelated) question, are there any ways to access the >> > clipboard? >> >> Not at the moment, but this is on our radar. Could you give me an >> idea of your specific use case? >> >> Erik >> >> >> >> > Thanks in advance, >> > Bob >> > >> > >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
