Open
Bug 1259063
Opened 10 years ago
Updated 3 years ago
On-screen keyboard flickers and is automatically dismissed while focusing the Password field
Categories
(Core :: Widget: Win32, defect, P3)
Tracking
()
People
(Reporter: adalucinet, Unassigned)
Details
(Keywords: regression, Whiteboard: tpi:+)
[Affected versions]:
- 45.0.1RC build 1
- 46.0b4 build 1
- latest Aurora 47.0a2 (from 2016-03-22)
- latest Nightly 48.0a1 (from 2016-03-22)
[Affected platforms]: Windows 10 64-bit on Dell Xps 12 and Surface Pro 2 devices
[Steps to reproduce]:
1. Launch Firefox.
2. Go to FxA Sign in /Create account page - E.g.: via about:preferences#sync and tap on Sign in button
3. Tap on the Password field.
4. Dismiss the on-screen keyboard - tap on X button.
5. Tap again on the Password field.
[Expected result]: The on-screen keyboard is displayed.
[Actual result]: The on-screen keyboard flickers and is automatically dismissed.
[Regression range]:
Not reproducible with 45.0a1 from 2015-12-01 - at step 5, osk is visible everytime the Password field is in focus.
[Additional notes]:
1. Also reproducible on 46 First Run page - https://www.mozilla.org/en-US/firefox/46.0/firstrun/, Yahoo and Gmail login pages.
2. As a side issue, when osk is dismissed and Menu panel or 'Show your bookmarks' button or Hello is selected, the keyboard is once again displayed.
Comment 1•10 years ago
|
||
I'm fairly sure this is a dupe. There are a number of issues because Windows itself magically does stuff for password fields. Please search the tree of existing bugs about the on-screen keyboard support. I'm also suspicious of this being a regression, but we can look at that in more detail. It's possible your steps are ever so slightly different from the existing bugs about the clash with Windows' support for password entry.
Comment 2•10 years ago
|
||
I ran a regressionwindow for this issue and reached the following pushlog:
https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=c151e3624f3247490add247ee03027b5056f0226&tochange=189cf9021f8b68bf645a719c51e5bd7d0d961de5
Keywords: regressionwindow-wanted
Comment 3•10 years ago
|
||
(In reply to Ciprian Muresan [:cmuresan] from comment #2)
> I ran a regressionwindow for this issue and reached the following pushlog:
> https://hg.mozilla.org/integration/fx-team/
> pushloghtml?fromchange=c151e3624f3247490add247ee03027b5056f0226&tochange=189c
> f9021f8b68bf645a719c51e5bd7d0d961de5
This doesn't match comment #0, because it says that this was not reproducible in December 2015, and those csets are from september 2015.
If you use an old build of 43 that includes the changes you identified, and in about:config, flip the pref ui.osk.require_tablet_mode to false, does that "fix" the problem ?
Flags: needinfo?(ciprian.muresan)
Comment 4•10 years ago
|
||
I have retested the issue on Nightly 43.0a1, Build ID 20150910030225 and changing that pref to false does not fix the issue.
Flags: needinfo?(ciprian.muresan)
Comment 5•10 years ago
|
||
(In reply to Ciprian Muresan [:cmuresan] from comment #4)
> I have retested the issue on Nightly 43.0a1, Build ID 20150910030225 and
> changing that pref to false does not fix the issue.
In that case can you trypush on top of efae2d9bba47 and test that build ? Because of the steps to reproduce it's not clear what is causing this issue - both csets are related.
It's also not clear to me how/why it's different from the other bugs relating to password fields (bug 1228298, bug 1211234 etc.) which don't match that regression window.
Flags: needinfo?(ciprian.muresan)
Comment 6•10 years ago
|
||
I've ran mozregression again but this time pursuing a fix on some odd behavior I have seen. It seems Bug 1140495 is causing this. Prior to this fix, the onscreen keyboard would not appear when tapping on the username field(tapping on the password field works), after this fix, tapping on the username prompts the onscreen keyboard to appear (and tapping on the password field makes the on-screen keyboard flicker and be dismissed)
Flags: needinfo?(ciprian.muresan)
Comment 7•10 years ago
|
||
(In reply to Ciprian Muresan [:cmuresan] from comment #6)
> I've ran mozregression again but this time pursuing a fix on some odd
> behavior I have seen. It seems Bug 1140495 is causing this. Prior to this
> fix, the onscreen keyboard would not appear when tapping on the username
> field(tapping on the password field works), after this fix, tapping on the
> username prompts the onscreen keyboard to appear (and tapping on the
> password field makes the on-screen keyboard flicker and be dismissed)
Jared, can you reproduce and/or do you have any idea why this would be the case?
Flags: needinfo?(jaws)
Comment 9•10 years ago
|
||
I can't reproduce this. I'm not sure why it may flicker, but I could guess that maybe there was/is some race between us losing focus and regaining focus.
Flags: needinfo?(jaws)
| Reporter | ||
Comment 10•10 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #8)
> Can you still reproduce this?
Yes, this is still an issue with latest 48.0a1 (from 2016-04-18), under Windows 10 64-bit (Dell Xps 12 and Surface Pro 2).
Flags: needinfo?(alexandra.lucinet)
Updated•10 years ago
|
Comment 11•9 years ago
|
||
I cannot reproduce this on Win 10 Surface Pro with latest Nightly 51.0a1, 20160812030200. Repeatedly opening and closing the OSK from a password field (such as login here on bugzilla) works smoothly.
Alexandria, do you see the bug with latest Nightly. If so, please re-open.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(adalucin)
Resolution: --- → WORKSFORME
Comment 12•9 years ago
|
||
I'm still able to reproduce this issue on a MS Pro 2 device running latest Windows 10 build using the Sync sign in form. This, indeed, does not reproduce with the bugzilla login.
Tested with latest 51.0a1 Nightly, build ID 20160825030226.
Status: RESOLVED → REOPENED
Flags: needinfo?(adalucin)
Resolution: WORKSFORME → ---
Updated•9 years ago
|
Priority: -- → P2
Whiteboard: tpi:+
Comment 13•7 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•