Chrome UDF

[seangriffin]

Chrome support for AutoIT is here! 

This UDF includes a Chrome Extension (http://developer.chrome.com/extensions/getstarted.html) and Native Messaging Host (http://developer.chrome.com/extensions/messaging.html#native-messaging-host) that integrate with a new Chrome UDF (Chrome.au3) to provide automation support for the Chrome browser.

Several steps are required to install the Chrome Extension and Native Messaging Host prior to using the UDF.  Please read the INSTALLATION section below.

REQUIREMENTS:

• Windows XP 32-bit, Windows 7 32-bit or Windows 7 64-bit
• AutoIt3 3.2 or higher
• Chrome v29 or later (earlier versions are untested)
• AutoIT for Google Chrome (Chrome extension - see below)
• AutoIT Chrome Native Messaging Host (see below)

INSTALLATION:

STEP 1: Install the AutoIT extension into Chrome.

Open the following link and download the file named AutoIT for Google Chrome.crx:

https://docs.google.com/file/d/0B_6JmwNIIZ06enotRTVFNVdKOXM/edit?usp=sharing

Note - you may be prompted to login with a Google account as this file is hosted on Google Drive.

In your Chrome browser click on the Chrome menu, then select Tools -> Extensions.  Drag the AutoIT for Google Chrome.crx file that you downloaded above, from Windows Explorer, into this page in Chrome.  You should now see AutoIT for Google Chrome listed in the Extensions page in Chrome.  Ensure that the Enabled checkbox next to AutoIT for Google Chrome is checked.  Also make sure the Allow access to file URLs box is checked (very important to make EXAMPLE 2 work below)!!

STEP 2: Install the AutoIT Chrome Native Messaging Host.

Open the following link and download the file named autoit_chrome_native_messaging_host_install.exe:

https://docs.google.com/file/d/0B_6JmwNIIZ06eDgxaVJPNUNxa28/edit?usp=sharing

Note - you may be prompted to login with a Google account as this file is hosted on Google Drive.

Run this file (autoit_chrome_native_messaging_host_install.exe).  An installation window will display.  Click the Install button.  The window will display "Completed" and you can click the Close button.

STEP 3: Install the Chrome UDF into AutoIT.

Scroll to the DOWNLOAD section below, and save the Chrome.au3 file into your AutoIT Include folder (C:Program FilesAutoIt3Include).

Please close your Chrome browser once you've completed these steps.

LIST OF FUNCTIONS:

_ChromeStartup($url = "about:blank", $chrome_path = "C:Program FilesGoogleChromeApplicationchrome.exe")

_ChromeShutdown()

_ChromeEval($javascript_expression, $timeout = 5)

_ChromeDocWaitForReadyStateCompleted($timeout = 5)

_ChromeInputClickByName($objname, $index = 0, $timeout = 5)

_ChromeInputClickByType($type, $timeout = 5)

_ChromeDocGetTitle($timeout = 5)

_ChromeDocWaitForExistenceByTitle($title, $timeout = 5)

_ChromeObjGetHTMLById($objid, $timeout = 5)

_ChromeObjGetHTMLByName($objname, $index = 0, $timeout = 5)

_ChromeObjGetHTMLByTagName($tagname, $index = 0, $timeout = 5)

_ChromeObjGetValueByName($objname, $index = 0, $timeout = 5)

_ChromeObjSetValueByName($objname, $value, $index = 0, $timeout = 5)

_ChromeInputSetCheckedByName($objname, $value, $index = 0, $timeout = 5)

_ChromeOptionSelectWithTextByObjName($option_text, $objname, $timeout = 5)

_ChromeOptionSelectWithValueByObjName($option_value, $objname, $timeout = 5)

_ChromeInputSetCheckedWithValueByName($input_value, $objname, $checked, $timeout = 5)

_ChromeObjGetPropertyByName($objname, $propertyname, $index = 0, $timeout = 5)

 

EXAMPLE #1:

This following example starts up Chrome and navigates to the URL http://www.december.com/html/demo/form.html.  It then automatically completes the HTML form in this page (a series of text, radio, and checkbox input elements and select elements) and clicks the Send this survey button.  The script waits for the next page to load, and retrieves the various elements from the page to the AutoIT console.

chrome_example.au3

EXAMPLE #2:

The following is an example of the automation of an offline HTML page (file URL).  First, download the file named chrome_udf_example_2.html to your C: folder:

https://docs.google.com/file/d/0B_6JmwNIIZ06SWduMjZGTVViNlU/edit?usp=sharing

Then run the following AutoIT script:

chrome_example_2.au3

Note that you must have checked the Allow access to file URLs box in the Chrome extension to make this work!

DOWNLOAD:

Latest Version - v0.5 (29/09/13)

Chrome.au3

Edited September 29, 2013 by seangriffin

[FireFox]

ahhh finally ! Nice find.

I will test it in the coming days, I may make some functions to improve the automation of the browser.

Br, FireFox.

[mLipok]

As you can see I am also interested.

I'll keep our fingers crossed.

[JohnOne]

Is the .exe and .crx created by yourself seangriffin?

[JohnOne]

Error from installer

Can't write C:\Windows\System32\python27.dll

 

[Mat]

Probably because the installer doesn't have permission to write to the system directory. Running as admin should fix it.

That said, the system directory is not the right place to be putting a dll dependency. That's just a little bit silly.

[JohnOne]

Never thought of that, Duh.

I installedpython275.

Anyway, example does not work for me.

Opens chrome navigates to test page but fills no fields and waits on line 106 of chrome.au3.

While TimerDiff($begin) < ($timeout * 1000)

     If FileExists($chrome_native_messaging_host_dir & "\output.txt") then ExitLoop
     sleep(100); here 
WEnd

And timeout does not appear to occur.

Win 7 32

Chrome version 29.0.1547.66

Edited September 10, 2013 by JohnOne

[seangriffin]

Is the .exe and .crx created by yourself seangriffin?

Hi JohnOne,

Yes I created both specifically for AutoIT.  I wrote them over the past couple of days.  It's been a rush, and it's still rough around the edges, but I'll do what I can to fix up any problems.

[seangriffin]

Probably because the installer doesn't have permission to write to the system directory. Running as admin should fix it.

That said, the system directory is not the right place to be putting a dll dependency. That's just a little bit silly.

 

It is silly, and it's the best I can do for the time being.  The "AutoIT Chrome Native Messaging Host" is a Python program compiled into a Windows 32-bit executable.  When I deployed it onto a fresh computer I noticed it still required "python27.dll".  The quick fix was to include "python27.dll" in the installer and write it to the WindowsSystem32 folder.  Works fine in Windows XP, but I see now that under Windows 7 it needs extra priviledges.  I need to find out how to resolve that "python27.dll" dependency.  I am new to Python (by the way).

[seangriffin]

Never thought of that, Duh.

I installedpython275.

Anyway, example does not work for me.

Opens chrome navigates to test page but fills no fields and waits on line 106 of chrome.au3.

While TimerDiff($begin) < ($timeout * 1000)

     If FileExists($chrome_native_messaging_host_dir & "\output.txt") then ExitLoop
     sleep(100); here 
WEnd

And timeout does not appear to occur.

Win 7 32

Chrome version 29.0.1547.66

 

Interesting that the timeout doesn't occur.  I wonder if this is another Windows 7 security issue.  I have a Windows 7 32-bit machine here but haven't tested on it.

Could you try running that block of code above in a separate AutoIT script?  It's a simple loop that checks for the existence of "C:Program FilesAutoIt3Chrome Native Messaging Hostoutput.txt", and if not found exits (ExitLoop).  If that is an endless loop under Windows 7 then something strange is going on.

[seangriffin]

I have updated the UDF to v0.2 now, with a few more functions and a new example (EXAMPLE #2).

Please try EXAMPLE #2, which is far simpler than EXAMPLE #1 which has the complexities of page load completion under Chrome.  I've run EXAMPLE #2 over and over repeatedly on my Windows XP machine and it hasn't failed.

Edited September 10, 2013 by seangriffin

[JohnOne]

Interesting that the timeout doesn't occur.  I wonder if this is another Windows 7 security issue.  I have a Windows 7 32-bit machine here but haven't tested on it.

Could you try running that block of code above in a separate AutoIT script?  It's a simple loop that checks for the existence of "C:Program FilesAutoIt3Chrome Native Messaging Hostoutput.txt", and if not found exits (ExitLoop).  If that is an endless loop under Windows 7 then something strange is going on.

Loop does not exit

File does not exist

only

autoit-chrome-native-messaging-host.exe

manifest.json

[Mat]

It is silly, and it's the best I can do for the time being.  The "AutoIT Chrome Native Messaging Host" is a Python program compiled into a Windows 32-bit executable.  When I deployed it onto a fresh computer I noticed it still required "python27.dll".  The quick fix was to include "python27.dll" in the installer and write it to the WindowsSystem32 folder.  Works fine in Windows XP, but I see now that under Windows 7 it needs extra priviledges.  I need to find out how to resolve that "python27.dll" dependency.  I am new to Python (by the way).

Putting it in the same directory as the program is the way you would normally do it with required dlls. Not sure how you are doing the install as I haven't had a chance to test your UDF yet.

[seangriffin]

I really messed that up didn't I 

Big apologies to anyone who already tried installing this.

I've made some major fixes now, and updated the top post with new links in the INSTALLATION section.

I've resolved many many issues including:

• the python27.dll file (it's now completely embedded inside the AutoIT Chrome Native Messaging Host)
• Windows 7 32-bit is now fixed (I now correctly use the roaming application data folder for the AutoIT Chrome Native Messaging Host)
• freeing up the AutoIT Chrome Native Messaging Host when Chrome is closed (to free up CPU and memory)

Windows 7 64-bit is still not working, but will be fixed very soon.

JohnOne and Mat, could you please re-test?  Firstly, remove the existing Chrome extension by opening Chrome, right-click on the jigsaw icon in the top right corner named "AutoIT for Google Chrome" and select "Remove from Chrome".  Then perform the 3 steps in the INSTALLATION section again, as the links have changed.  Let me know how you go.

Cheers guys,

Sean.

Edited September 12, 2013 by seangriffin

[seangriffin]

Windows 7 64-bit is now supported.

I've tested the UDF with Windows XP 32-bit, Windows 7 32-bit and Windows 7 64-bit.  They all work as expected.

Cheers,

Sean

Edited September 12, 2013 by seangriffin

[ozmike]

This rocks!

[JohnOne]

Before I try this again, can you tell me what registry keys have been added or modified which causes the process to run at startup.

And any other keys please?

[seangriffin]

Before I try this again, can you tell me what registry keys have been added or modified which causes the process to run at startup.

And any other keys please?

 

A total of one key is written to the registry.

It's location is HKLMSoftwareGoogleChromeNativeMessagingHostscom.sean.consoleread(Default).

It's value is %APPDATA%AutoIt3Chrome Native Messaging Hostmanifest.json.

This key is a prerequisite of Chrome for a Native Messaging Host.

[JohnOne]

Cheers Sean.

[JohnOne]

I don't know what I've done to balls all this up, but it still is not working for me.

I redownloaded and installed native messaging host, still just navigates to the page and does nothing