Form Automation Question – Mobiscroll Test Macro

[JMichaelTX]

@slothinker

I'd highly recommend adding a prominent disclaimer or asterisk which indicates that many (%-age?) of Web site forms cannot be reliably automated with KM owing to a variety of variables such as the above-described "randomly generated IDs".

At the time this KM feature was introduced, there were very few web forms that used dynamically generated IDs and classes. Since then, for some reason, more and more web pages are using this method.

But I do agree with your suggestion that the KM Wiki Article Browser Form Actions actions should be revised to add a notice at the top that those Actions may not work with some web pages.

@slothinker

Any full automation provided by an app such as KM should include highly reliable and reproducible management/control of commonly encountered Web form widgets such dropdown lists, buttons, etc. and should work on all major browsers IMO

KM clearly states that its Actions, Tokens, and Functions that are web specific work only with Safari and Google Chrome (and Chrome-based browsers for FrontBrowser items).

KM is highly reliable, but everyone needs to recognize that due to the complex nature of web pages, there may be some pages where KM will not work as designed.

And even with those web pages, you may be able use use KM tools like Execute a JavaScript in Browser actions to get and set these dynamic web form fields. I have often used querySelector to work on these pages.

@slothinker

I, for one, would not have purchased a license had I been made aware that many web forms (%-age?) cannot be effectively controlled (automated) by KM.

Sorry that you have encountered problems with some web pages.
However, the scope of KM is much, much broader than just automation of web pages.

Please take a look at Best Macro List -- KM Forum for some really good examples of how KM can automate all aspects of your Mac workflows.