>>Yes, nearly identical, as IE is activeX. Did a lot of that last century when IE was dominant, but today more and more devs want to escape IE problems. Also I found newer versions of IE to be less stable as activeX components than in IE4-IE6 times, but that might be a misperception as back then I spent much more time roboting WebBrowser and InternetExplorer.Application.
>>
>>Unless your need is a short time temp solution, implement with different tool set.
>
>If you know of a different browser ActiveX that we can use, please share. That would bring dozen years of torture to an end.

Definately no certain knowlegde about the specific question - but also the suspicion that the question itself is too specific ;-))

Automating IE/MsHTML probably is today the Pareto-friendly way to handle most (client side) web/internet connected scenarios above SOAP/REST level, as the combination of display with access to internal structure plus our vfp engine is nice.

But since more fwks currently shun IE and its problems in exchange for leaner code, that particular approach has diminishing targets.
For long term solutions I'd look at the specific use case and work with the tool set best for it.

There is a product CLAIMING to do automating across browsers for $99 now
https://imacros.net/overview/web-testing/
which I have not tried yet, since I had no task recently in that area. If you test, pls. notify me of results and conclusions ;-)

Among the tools to consider are

- Selenium coupled with self written script (generation),
- client side injected scripts (Grease- Tampermonkey communicating with data store/biz logic via HTTP)
- Injecting your Debug/Roboting sources into Electron (did something similar with NW.js as a test, benefit direct access to host)
- headless chrome
- no-GUI solutions like Beautiful Soup or lxml (Did not check out Puppeteer or Cheerio, which might be better since already in JS and might be useful both in *monkey or Electron )

Keep me posted if you dip in any of those

thomas