Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

On screen keyboard now working on Surface Pro 3

  • 3 uphendule
  • 268 zinale nkinga
  • 2 views
  • Igcine ukuphendulwa ngu adskee

adskee
adskee
more options

I have upgraded to Windows 10 and moved from Chrome to Firefox. However when I select any text input field in Firefox, the on screen keyboard will not appear when I'm in Tablet Mode without a physical keyboard attached. The on screen keyboard works fine in all other apps.

I didn't have Firefox before the upgrade to Windows 10 so not sure if it's related to this or not.

I have upgraded to Windows 10 and moved from Chrome to Firefox. However when I select any text input field in Firefox, the on screen keyboard will not appear when I'm in Tablet Mode without a physical keyboard attached. The on screen keyboard works fine in all other apps. I didn't have Firefox before the upgrade to Windows 10 so not sure if it's related to this or not.

Isisombululo esikhethiwe

thanks for bringing this up, i can reproduce it on a device with a pen input (regardless if win10 is in tablet mode or not) and will file a bug report for it.

edit: turns out this is already worked on in bug #1007063

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 2

All Replies (3)

adskee
adskee Umnikazi wombuzo
more options

I spoke to Microsoft Surface Support today. They said the issue is because Firefox have not released an update for Windows 10. Chrome did it yesterday but Firefox haven't yet. They said this would fix the problem. Don't know if it's true or not.

philipp
philipp
  • Moderator
more options

Isisombululo Esikhethiwe

thanks for bringing this up, i can reproduce it on a device with a pen input (regardless if win10 is in tablet mode or not) and will file a bug report for it.

edit: turns out this is already worked on in bug #1007063

Okulungisiwe ngu philipp

adskee
adskee Umnikazi wombuzo
more options

Thanks Philip, that bug report made interesting reading. Sounds like a complicated issue. The developers provided a short term workaround near the bottom of the thread, so that was really useful.