oh gosh, wasn't there an add-on that forced UIA in Chrome for NVDA? Or am I dreaming of this. Would sure help me as enabling the flag: "Override software rendering list
Overrides the built-in software rendering list and enables GPU-acceleration on unsupported system configurations. – Mac, Windows, Linux, ChromeOS, Android
#ignore-gpu-blocklist" breaks all NVDA cursor tracking and reading in multiline controls. I kid you not. Test it yourself, enable it and restart. No idea what this does to break #NVDASR but there it is, it breaks it. I could repro it on two machines, go ahead. Chrome://flags is where it's at. (ah yes, this is now in NVDA's advanced prefs, yay! no add-on needed!)
And yup. Doing that setting, to use UIA in Chromium and Edge to yes fixed it all. Wow, facepalm moment, ugh.