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 don't know what you're trying to do, but you might want to look into > Launch Services (and potentially a language that's not java). I'm writing Chrome support for a browser test automation tool (WebDriver, which is soon merging to become Selenium 2.0 [1]). Unfortunately, Java is a requirement (actually, so are half a dozen other languages in the future). As these tests tend to be run on machines with no user interaction, having some solution to this is very important. 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]). 1: http://selenium.googlecode.com 2: http://my.opera.com/core/blog/2009/03/06/test-automation-with-operawatir --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
