Closed Bug 1643955 Opened 6 years ago Closed 6 years ago

nö on-screen keyboard in ff77

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

Product:
Core
Component:
DOM: UI Events & Focus Handling
Version:
76 Branch
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1648534

People

(Reporter: Richter.com, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0
Firefox for Android

Steps to reproduce:

After update ff 76 to 77 no automatic on-screen keyboard
After downgrade to ff76 on-screen keyboard appears as usual when a input fiele is selected. Hardware: Surface pro 6

Actual results:

no automatic on-screen keyboard

Expected results:

automatic on-screen keyboard

See Also: → 1643878

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → DOM: UI Events & Focus Handling
Product: Firefox → Core

Pls. excuse my igborance, but which "component" are you talking about?
Do you refer to my Surface Pro 6?
The error is still reproducable in Version 78.0.2.

Is it a duplicate of bug 1648534?

Severity: -- → S2
Flags: needinfo?(m_kato)
See Also: → 1638534

Yes If Widnows 10 2004.

Richter.com, what Windows version do you use? Windows 10 2004?

Flags: needinfo?(m_kato) → needinfo?(Richter.com)

Hi Makoto.

I am still using 1909 built 18363.900 as MS does not support 2004 on my surface pro 6 already.

Additional info:
I am using the Deskto mode on my tablet.
Some hints seemed to suggest,
that the onscreen keyboard is supposed to work fine in tablet mode.

This is only half the truth!

If I tab (in tablet mode) on an input field,
the onscreen-keyboard pops up, but the context menue opens as well and has the focus.
So I have to tab the inputfield once again, before I am able to enter characters.

Wolfgang

Flags: needinfo?(Richter.com)

Thanks. Actually although we respect "Automatically show the touch keyboard in windowed apps when there's no keyboard attached to your device." in setting app, but it isn't enough. If you turn off then turn on this option, it will work well.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE

Hi Makoto.

Thank you for your support.
But I cannot confirm your suggestion:
" If you turn off then turn on this option, it will work well."

Therefore I'll be a bit more specific.
The behavior after turn off/turn on is the same as before.
There is a slight difference whether I will tab in the adressfield or e.g. the google search field.

In the adressfield the osk will pop up nearly always showing the contextmenue.
In the google search field I may be lucky once in 20 to 30 times. Sometimes not at all.
If the osk apears, it will do so here without showing the context menue!

Wolfgang

What value of ui.osk.debug.keyboardDisplayReason in about:config when this occurs?

Unfortunately, until Firefox 76, our code is broken on Windows 10 RS1+, so I have fixed it correctly by 77, so I would like to this about:config's value.

It's IKPOS:
Keyboard presence confirmed.

detect_physsical keyboard -> true
osk.enabled -> true
osk-path -> empty
require_win10 -> false

You need to log in before you can comment on or make changes to this bug.