Automating Chrome with AutoHotkey Script to Handle EventListeners & custom edit fields
Notes on handle EventListeners & custom edit fields
00:09 When web scraping, often there will be buttons I can’t press, text that doesn’t get “acknowledged” that it has been entered, etc. Continue reading
You ever plugging along on web scraping a page and have a problem with an element (drop down, edit field, radio button, etc) not updating? Chances are the page has an EventListener watching that element for a specific Event type. We used to be able to reliably “click” an element or send .fireEvent(“onchange”) / .fireEvent(“onclick”) however more and more pages are using this newer approach where they build an Event Listener and monitor for events on a given element.
If you’re not a programmer (like me), this was very problematic to deal with as the EventListener is located in a different place in the DOM. In the below video I walk through how to spot the problem and offer up a couple of solutions (like Visual Event) that should greatly help. The second video below demonstrates using my updated AutoHotkey syntax writer.
Triggering an EventListener on a page
Updated AutoHotkey Syntax Writer
Here I demonstrate using my updated AutoHotkey Syntax writer to provide the needed information for the Events.
Automating Chrome with AutoHotkey: handle EventListeners & custom edit fields
If you’re loving this, please consider donating to GeekDude!
