Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

On screen keyboard now working on Surface Pro 3

  • 3 trả lời
  • 268 gặp vấn đề này
  • 2 lượt xem
  • Trả lời mới nhất được viết bởi 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.

Giải pháp được chọn

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

Đọc câu trả lời này trong ngữ cảnh 👍 2

Tất cả các câu trả lời (3)

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.

more options

Giải pháp được chọn

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

Được chỉnh sửa bởi philipp vào

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.