Closed
Bug 1234641
Opened 10 years ago
Closed 3 years ago
Onscreen keyboard comes up when using Bluetooth keyboard on Windows 10 (Surface 3)
Categories
(Core :: Widget: Win32, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: pinecoding, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.10586
Firefox for Android
Steps to reproduce:
Run Firefox on Windows 10 Surface 3 with Apple Bluetooth keyboard and Microsoft Bluetooth mouse, then click on a text field. Doesn't matter what site I am browsing.
Actual results:
Whenever I click on a text field, the on screen keyboard comes up. The on screen keyboard goes away as soon as I type a key on the Bluetooth keyboard. This happens all the time, and it is a recent problem: have only seen this issue for the last few days; seems to have been caused by a Firefox update.
Expected results:
The on screen keyboard should never come up when the Bluetooth keyboard is connected. For example, in order to file this bug I am using the Microsoft Edge browser, and the on screen keyboard has not come up once, in spite of all of the text fields.
Updated•10 years ago
|
Component: Untriaged → Editor
Product: Firefox → Core
Comment 1•10 years ago
|
||
We will be changing the bug from Unconfirmed to New so that items with a component no longer display unconfirmed after a review
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•10 years ago
|
||
¡Hola!
Does this bug exists if you use Nightly from https://nightly.mozilla.org/ ?
¡Gracias!
Alex
Flags: needinfo?(pinecoding)
Updated•9 years ago
|
Component: Editor → Widget: Win32
Updated•3 years ago
|
Severity: normal → S3
Comment 3•3 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.
For more information, please visit BugBot documentation.
Flags: needinfo?(pinecoding)
Comment 4•3 years ago
|
||
:cmartin, does this look like a duplicate of one of the touch-input bugs you're already looking at?
Flags: needinfo?(cmartin)
Comment 5•3 years ago
|
||
Unfortunately, there's really no way to know without knowing if the user is still experiencing this issue. It's been 7 years, so a lot could've changed between now and then. I'm just going to close the bug as INCOMPLETE, and if it's still broken it will hopefully be fixed by one of the other input bugs.
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(cmartin)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•