Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

The Windows 10/11 on screen keyboard has been broken in Firefox if Taskbar is set to "auto-hide" FOR YEARS!!!!

  • 4 件の返信
  • 1 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: Paul

more options

Basically the subject line. Ever since sometime in 2020, the Windows 10/11 on screen keyboard has been COMPLETELY broken in Firefox if the Windows Taskbar is also set to "automatically hide"! If a text entry box is selected, the keyboard will pop up for less than a second and then disappear.

Now in W10 the on screen keyboard is only broken in Firefox if in "tablet mode", but as that's the "only display mode" available in W11 it's COMPLETELY & UTTERLY broken in the newer OS!!! This means that while a workaround "fix" exists for W10 by changing the on screen keyboard's settings to have the same behavior in tablet mode as in desktop mode, in W11 the ONLY WAY to make the keyboard WORK AT ALL is to turn off Taskbar auto-hiding, which is simply UNACCEPTABLE on small screen devices!!!

And this has been broken and reported to you guys COUNTLESS TIMES for literally FREAKING YEARS at this point!!! Do you need a patch from Microsoft or something to fix this bug, because this is getting freaking absurd at this point...

I've been a diehard Firefox user for literally DECADES at this point, but I WILL LEAVE if this doesn't ACTUALLY get fixed in the near future!!!

Basically the subject line. Ever since sometime in 2020, the Windows 10/11 on screen keyboard has been COMPLETELY broken in Firefox if the Windows Taskbar is also set to "automatically hide"! If a text entry box is selected, the keyboard will pop up for less than a second and then disappear. Now in W10 the on screen keyboard is only broken in Firefox if in "tablet mode", but as that's the "only display mode" available in W11 it's COMPLETELY & UTTERLY broken in the newer OS!!! This means that while a workaround "fix" exists for W10 by changing the on screen keyboard's settings to have the same behavior in tablet mode as in desktop mode, in W11 the ONLY WAY to make the keyboard WORK AT ALL is to turn off Taskbar auto-hiding, which is simply UNACCEPTABLE on small screen devices!!! And this has been broken and reported to you guys COUNTLESS TIMES for literally FREAKING YEARS at this point!!! Do you need a patch from Microsoft or something to fix this bug, because this is getting freaking absurd at this point... I've been a diehard Firefox user for literally DECADES at this point, but I WILL LEAVE if this doesn't ACTUALLY get fixed in the near future!!!

すべての返信 (4)

more options

Hi

This appears to be the first time that you have reported this issue to us. In what way is the keyboard not working, what appears to be broken?

more options

... I literally explained in pretty fine detail exactly what the problem was already. If Firefox is used in a "Maximized Window" either literally anywhere in Windows 11 or in Windows 10's "Tablet Mode" while the Windows Taskbar is set to "automatically hide", it will COMPLETELY break the Windows on screen keyboard's functionality! As in if you "click" on literally any kind of text entry box while Firefox is maximized & the Taskbar is hidden, the on screen keyboard will only pop up for a mere fraction of a second before disappearing. This process will repeat itself no matter HOW MANY times or different text boxes you try, leaving one without ANY method of text input on a tablet.

It's the same problem described right here, all over Reddit, and in MULTIPLE other help requests & official Mozilla bug reports.

This one -> https://bugzilla.mozilla.org/show_bug.cgi?id=1678953

more options

Hell, turns out the bug report link I sent you was actually even labeled as a damn duplicate of this even earlier one! THAT'S how ridiculously freaking long this has been completely and utterly broken for!

https://bugzilla.mozilla.org/show_bug.cgi?id=1749484

more options

That bug appears to have been filed very recently. I recommend that you add feedback to that bug to provide extra information to our developers and raise its profile so that hopefully it can be looked at soon.