On Wed, Sep 2, 2009 at 1:07 AM, Daniel Wagner-Hall <[email protected]>wrote:
> On Tue, Sep 1, 2009 at 11:26 PM, Nico Weber<[email protected]> wrote: > > This is probably because of the launcher changes that Mark made. When > > I start Chromium from a terminal, it opens in the background too. > > `osascript -e 'tell app "Chromium" to activate'` works, though (it > > opens chromium and makes it frontmost), so perhaps you can use that > > from Java somehow? > > This is fine on Mac, and if you only have one instance of Chrome, > unfortunately neither is the case here... > I think Nico didn't notice your "on Vista" comment. To have Chrome being the only browser out there which > doesn't support automated testing would seem to me to be a huge blow > (in fact, Opera at completely the other end of the spectrum and are > building in hooks for test automation! [2]). Please don't overgeneralize. Chrome has a fairly extensive automation layer that was built for the 16 other times that groups at Google came to us wanting to do automated testing in Chrome. I don't know the solution to your particular bug (which certainly sounds like a bug, and you should file at crbug.com), but to say we "don't support automated testing" is about as far from the truth as you can get. PK > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
