Closed Bug 1264294 Opened 8 years ago Closed 5 years ago

Touch Keyboard no longer available

Categories

(Core :: Widget: Win32, defect)

45 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: dbondo, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160407164938
Firefox for Android

Steps to reproduce:

Have to minimize Firefox to get touch keyboard, and try to maneuver back and forth between Firefox search window and touch keyboard.


Actual results:

Had touch keyboard working in Taablet mode before being updated to Firefox 45.0.1.  Now the Touch Keyboard no longer works for the address and search windows in Tablet mode.  It does come up for Websites.  This is a Dell Laptop Inspiron 13-7353, running Windows 10 version 10.0.10586, 64 bit, 8GB RAM.  This occurred about the beginning of April 2016.


Expected results:

When in tablet mode and the search window (or a website input window) is activated the on screen touch keyboard should be activated, which it no longer is.
Component: Untriaged → Widget: Win32
Product: Firefox → Core
How do you activate these fields? With the keyboard, a mouse, or by touching the screen, or using an external application, or...?

If you open about:config and filter for "ui.osk", what does the ui.osk.debug.keyboardDisplayReason pref value say?
Flags: needinfo?(dbondo)
Hm, and/or does using developer edition ( https://www.mozilla.org/en-US/firefox/channel/#developer ) have this fixed? Based on what changed in 45, I suspect this might be related to bug 1245038 which got fixed for 47 (currently developer edition) .

2019-03-06

This bug is part of a group of bugs which have had an open needinfo for at least 12 weeks.

The request for information has not been answered, and we can't move forward on the bug so we are closing it.

If the defect is still present, please reopen this bug with an updated report.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.