chrome automation - chrome.au3 ?

[Alterlife]

I would like to know how I can get the equivalent of ie.au3's functionality for chrome... and I'm lost.

I've got the classname for the HTML Rendering window, but how do I access the controls created under it by each page?

I don't even know where to start, so any thing to get me on my way would be useful.

[PsaltyDS]

We have the great IE.au3 UDF because Microsoft chose to expose a COM interface to the DOM in IE, and Dale put a very usable AutoIt function wrapper on that.

There is a FF.au3 UDF for Firefox only because you can install a plug-in for FF that exposes a COM interface that is not normally there.

So, the question is: Does Chrome expose a COM interface, or allow a plug-in that will? The question would be the same if you want to use AutoIt scripting with Safari, Opera, etc. What API does it expose that AutoIt can use?

[Mat]

Its open source. Anyone wanna go digging?

[Alterlife]

Ouch! That's too bad .

I did a few google searches for "Chrome COM", "Webkit COM" etc, there's nothing that I can find... I guess this means I'm sticking to automating ie!

Thanks for your help!

[JohnOne]

Way over my head this sort of stuff, but found this.

ChromeWatir has an API similar to Watir and used to drive Google Chrome browser. As of now it works in Windows platform. The support for other platforms will be worked on once Chrome browser gets ported to other platforms like Linux and OSX.

http://wiki.openqa.org/display/WTR/ChromeWatir

[doccy]

found this

http://dev.chromium.org/developers/design-documents/extensions/gleam-api

[ProgAndy]

Maybe this is useful for you http://bitbucket.org/kzys/chrome-repl/wiki/Home

(works similar to MozRepl which is used in FF.au3)

[atzoref]

There is some updates on this issue? Someone maybe created an *.au3 file for Chrome?

Because I have some problems with the FF.au3

and IE is very slow.

Thanks

[water]

As far as I know ther is no UDF for Chrome right now.

[MouseSpotter]

My current view is that Google does not trust external access to Chrome, refuses to expose the DOM to external programs and therefore requires the user to install a plugin for each application.

I strongly doubt that the NPAPI even allows exposure to external programs.

Annoying as it is to have this restriction - it does make the browser more secure.

[FireFox]

Well I have tried two times to make a library for this, but hit a wall each time. I don't have the faith to try again.

[junkew]

Search for ui automation in the forum. Chrome supports accessibility. And ui automation can be done thru autoit.