Forum Discussion
Beta 79.0.309.51 problems with touch keyboard
- Dec 19, 2019
matsmcp I can also talk to the team about porting the fix for that bug to Dev/the next Beta, but I'm not sure what the bar is for getting fixes in.
matsmcp Thanks for letting us know! We are currently aware of one issue that has been affecting the older touch keyboards. If you have an older version, the interim recommendation is opting-out/turning it off for now, if possible.
Please loop back if you're either already using the newest keyboard or experience any other bugs.
Fawkes (they/them)
Project & Community Manager - Microsoft Edge
- matsmcpDec 29, 2019Iron Contributor
Deleted josh_bodner Neon01
Just a quick feedback. Latest Canary has the fixes and works well.
Happy new year
- DeletedDec 29, 2019
- matsmcpDec 17, 2019Iron Contributor
Deleted
Hi, yes it's the older keyboard on this device. Running on 1607 LTSB so it doesn't have the newer keyboard. I believe it's 1607 and 1703 that have that keyboard
It's not exactly the same Issue as in dev/canary either. On those the failure rate was 100%. On beta it's maybe 50% and I haven't found a good method to provoke it either
- Neon01Dec 17, 2019Iron Contributor
This issue about the virtual keyboard/SIP (Software Input Panel) not coming up is based on the changes inside the Chromium engine, and affects all chrome driven browsers for the Windows platform.
The bug is meanwhile fixed in Google Canary #81.0.3999.0 , see https://bugs.chromium.org/p/chromium/issues/detail?id=1022295 for details.
I hope the Edge Team will update to the new Chromium engine soon, so this will be fixed for us Edge users, too.
To check the version of the Chromium Engine type edge://version
Then in the section "User-Agent" look for the entry: Chrome/80.x.xxx.x