If I'm correct then that bug was the one that required "--force-renderer-accessibility" to be added to the Chrome parameters. I've been using this parameter all the time since the bug was reported. As a test I've just removed it from the command line and retried WebAutoType. I've found it works as expected on all but one of the websites I tried.
The only one that failed was m.skybet.com. When the "--force-renderer-accessibility" parameter is added WebAutoType works as expected. I'm running the latest version of Chrome - 87.0.4280.88 (Official Build) (64-bit).
I'm not after a fix, but you may still want to mention the need for "--force-renderer-accessibility" as there may be other websites that have the same issue?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's very strange, I can't find any reason why it should make a difference which website it is. However, I will leave in the readme the mention of "--force-renderer-accessibility" as a general first thing to try if there are any issues with Chrome.
Not just for this, but they have form for breaking accessibility detection every so often, so you never know whether it will work well in the next release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Bruh.. I just read this entire bug page:
https://bugs.chromium.org/p/chromium/issues/detail?id=881753
..and got to the end and saw where you said 'Yep, it's fixed now.'
You want to update your description here on SourceForge to edit that part out? ;)
Heh, yep, good catch, thanks for the suggestion.
If I'm correct then that bug was the one that required "--force-renderer-accessibility" to be added to the Chrome parameters. I've been using this parameter all the time since the bug was reported. As a test I've just removed it from the command line and retried WebAutoType. I've found it works as expected on all but one of the websites I tried.
The only one that failed was m.skybet.com. When the "--force-renderer-accessibility" parameter is added WebAutoType works as expected. I'm running the latest version of Chrome - 87.0.4280.88 (Official Build) (64-bit).
I'm not after a fix, but you may still want to mention the need for "--force-renderer-accessibility" as there may be other websites that have the same issue?
That's very strange, I can't find any reason why it should make a difference which website it is. However, I will leave in the readme the mention of "--force-renderer-accessibility" as a general first thing to try if there are any issues with Chrome.
Not just for this, but they have form for breaking accessibility detection every so often, so you never know whether it will work well in the next release.