Not working in Chrome v117

[usernamelectro]

Problem

It seems that KeyLayoutAutoSwitch doesn't work in Chrome, since it was updated to v117.0.5938.63 (Official Build) (64-bit)

Things I've tried

1. Changing accessibility features through chrome flags, without success:

2. Starting Chrome using --force-renderer-accessibility switch, without success:

Config

KeyLayoutAutoSwitch v2.1.1
Windows 11 22H2 Build 22621.2283

[AlexVallat]

I've just tried it with Chrome portable 117.0.5938.63 and it seems to be working fine. I'm on Win 10, but I doubt that makes a difference. Check chrome://accessibility/, the first two checkboxes ("Native accessibility API support" and "Web accessibility") should both be checked. That should happen automatically, but in case it doesn't you can check them manually.

[usernamelectro]

It works now, thanks!
I wasn't aware of these options at all, so this should also be pointed out in the readme for the others.

[nitzan-blink]

hi @AlexVallat, I have the same issue in Edge.
when going to edge://accessibility/ the two checkboxes you mentioned are off.
after I turn them on, and do Clear Previously Visited, then it will work, but only as long as I didn't restart Edge.
after restarting Edge, these two checkboxes are again off.
adding the --force-renderer-accessibility flag to Edge shortcut does not enable them.
do you have any clue?

[AlexVallat]

I'm not sure why Edge isn't automatically enabling those options. As far as I can tell it's getting the same auto-detection hook called as Chrome does.

If I create a shortcut to "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --force-renderer-accessibility that works for me, though.

[nitzan-blink]

@AlexVallat I just tried it again, and it seems that the edge process has to be killed (via task manager) for the shortcut arguments to apply.
when doing that, they work.
I will test it some more, and update if it stops working.
thanks!