In this video we discuss why Rufaydium has so much potential, some of the things we hope it has built into it, and the alternatives like Chrome.ahk and Selenium.
Automate Chrome with Rufaydium and AutoHotkey First Tutorial
Our first Rufaydium tutorial we walk through how to set it up and how to Automate Chrome with Rufaydium
How to use a Chrome Profile with Rufaydium and AutoHotkey
A while back someone wrote me saying how IE is dead and wondering how we can automate other browsers. While IE is definitely on it’s death-bed, I do still automate IE for sites that will let IE load. Someone mentioned that Windows 11 completely removes Internet Explorer thus, if you’re running Windows 11, automating IE is not an option. I looked into this and had some very interesting discoveries:
The IWB2 Learner tool works within Edge when in “IE Mode”
In Windows 11, you can add IE back and still use it in IE mode. (I’ll document how I did this in a later video)
When I realized the above, I played with Edge (in IE Mode) in Windows 10 & Windows 11 and was able to connect to the DOM! Granted my approach sucked but I asked Tank (Charlie Simmons) to take a look at it and he borrowed on the concept and re-wrote what i did into something that is decentily reliable. You can get the download here
Here’s a video showing how I use AutoHotkey to Automate IE from within Edge!
AutoHotkey script for Automating Chrome to Set Text & Click a button
#Include ;Remember to put Chrome in your library folder
#SingleInstance,Force
;**************************************
page:=Chrome.GetPageByTitle("AutoHotkey Community","contains") ;This will connect to the second index of a specific tab
If !IsObject(page){
MsgBox % "That wasn' t object / the page wasn't found"
ExitApp
}
page.Evaluate("document.querySelector('#keywords').value ='Chrome.ahk'")
Variable =document.querySelector('#keywords').value ='Chrome.ahk'
page.Evaluate(Variable)
var:="duh"
page.Evaluate("document.querySelector('#keywords').value ='" var "'")
page.Evaluate("document.querySelector('#search > fieldset > button').value ='Chrome.ahk'")
Notes for Automating Chrome to Set Text & Click a button
00:36 Go to AutoHotkey.com/boards/
00:44 Connect to tab using Chrome.GetPageByTitle(“AutoHotkey Community”) ;the default matchtype is “starts with”
01:23 Look at page structure using right-click and Inspect. This opends Devtools with that element selected.
01:46 It has an ID of “keywords”, copy js path. Which will give you queryselector(“#keywords”)
02:26 Use the .value to set some text in that box.
04:01 Make sure inside the JavaScript you use the “=”, not “:=”
04:15 Some people don’t want to have to learn JavaScript. When using Chrome, you’re going to have to learn JavaScript.
04:56 When using Chrome.ahk, we’re injecting JavaScript. So best to learn
05:54 The button is right next to the input. You can go back to the page and right-click the button, then hit Inspect
06:13 Test the new js path. Instead of using .value, use .click
06:42 Test in Chrome developer tool
07:18 When running an Evaluate method, it waits for the previous Evaluate to finish (so no need to sleep between them).
07:44 If you run into a problem where you think it is happening too quickly, check the forum for some solutions
08:40 Sometimes what you want to input won’t always be a static string. If you’re trying to reference a variable, you need to use the expression syntax. In an expression, you’re not just assigning text, you’re doing math or making function calls.
page.Evaluate(“document.querySelector(‘#keywords’).value ='” var “‘”) “‘”)
10:48 This works because AutoHotkey splits everything up on a given line. First is a name of a function, then says this is inside the function, then this is text inside a function. Then builds from left to right as to the string that will be used.
12:15 AutoHotkey proceeds left to right when evaluating an expression
12:40 when you use := you’re in expression assignment mode.
13:25 With just single = you’re in plain-text mode. It reads it as text
15:00 When automating a site, you don’t know what kind of buffer’s they have to prevent scraping / botting.
15:49 When you start automating, you might start seeing Captcha’s everywhere
16:04 Sites get really good at looking like a normal site to a user, but looking like an impenetrable fortress to code
16:36 If your variable contains a single quote or other special charachters, JavaScript will interpret it as code instead of text.
Not mentioned in Video but GeekDude wrote me after
You can escape JavaScript code using Coco’s JSON library does actually do that escaping that we discussed when talking about putting data on the page. The syntax for invoking it looks like this:
A while back someone wrote me saying how IE is dead and wondering how we can automate other browsers. While IE is definitely on it’s death-bed, I do still 
automate setting text in a search field and then hitting the button to submit the search.
