You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to reproduce
Using Windows 11, enable touch on–screen keyboard.
Enable suggestions, which should show on the top line of the on screen keyboard. Type in Chrome to test that it works.
Try to type in Telegram Desktop's text box in a chat, or search.
multilingual suggestions on, English from US used, with UK English as secondary. Doesn't seem to matter though.
After some Googling, all I can find is that swipe and predictions only work in "certain kinds of text boxes". Third party apps do work (works fine in Discord for example).
Expected behaviour
Suggestions should appear on top of the keyboard, and swiping your finger should type words that match the keys you swiped over.
Actual behaviour
Not swipe nor predictive suggestions work.
Operating system
Windows 11
Version of Telegram Desktop
5.14.2
Installation source
Microsoft Store
Crash ID
No response
Logs
The text was updated successfully, but these errors were encountered:
Steps to reproduce
Steps to reproduce
Using Windows 11, enable touch on–screen keyboard.
Enable suggestions, which should show on the top line of the on screen keyboard. Type in Chrome to test that it works.
Try to type in Telegram Desktop's text box in a chat, or search.
multilingual suggestions on, English from US used, with UK English as secondary. Doesn't seem to matter though.
After some Googling, all I can find is that swipe and predictions only work in "certain kinds of text boxes". Third party apps do work (works fine in Discord for example).
Expected behaviour
Suggestions should appear on top of the keyboard, and swiping your finger should type words that match the keys you swiped over.
Actual behaviour
Not swipe nor predictive suggestions work.
Operating system
Windows 11
Version of Telegram Desktop
5.14.2
Installation source
Microsoft Store
Crash ID
No response
Logs
The text was updated successfully, but these errors were encountered: