Focused input in closed dialog
Reported by
karlsson...@gmail.com,
Nov 4 2016
|
||||||||||||
Issue descriptionExample URL: https://jsfiddle.net/fdcrxtct/3/ Steps to reproduce the problem: 1. Open a dialog with an input that is autofocused. 2. Close the dialog. 3. Use a handheld scanner that sends keystrokes (bluetooth scanner in my case) to scan a barcode. What is the expected behavior? The keyup event should be logged in the console. What went wrong? When the dialog is opened the autofocus sets focus on the input. (The autofocus is crucial as this works fine without it). When the dialog then is closed the document:keyup event stops firing. Even reloading the page doesn't make the keyup event work again. Clicking the omnibox then focusing the page makes it work again. This issue is not present in chrome for mac. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? N/A Chrome version: 54.0.2840.68 Channel: stable OS Version: 5.0.1 Flash Version:
,
Nov 5 2016
Device: Lenovo Tab 2 A10-70 running Android 5.0.1.
,
Nov 7 2016
aelias@ any idea?
,
Nov 8 2016
,
Feb 21 2017
Any news on this? Just ran into this again. This time with @angular/material and tabindex (autofocus).
,
Aug 23 2017
Same issue with the keypress event: 1. Go to https://s.codepen.io/schnouki/debug/prKedL/yYMyLDXQjEZk 2. Tap the body to make the input lose focus 3. Scan a barcode (in my case "24..." with a handheld bluetooth barcode scanner Expected result: see "Keypress event: 2", "Keypress event: 4", ..., "Keypress event: Enter" appear Actual result: "Keypress event: Enter" appears, and that's it. Now tap the omnibox, tap the page again, and scan a barcode again: the code behaves as expected. OnePlus One, Android 7.1.2 (LineageOS 14.1-20170807-UNOFFICIAL-Sultan-bacon), Chrome 59.0.3071.125. Not sure if it's relevant, but I use SwiftKey as my main (virtual) keyboard, and every keyboard is set to the French (AZERTY) layout, including the barcode scanner. Now some more fun: on a French keyboard, 2 is Shift+é (and all digits are Shift+keys). And when listening to "keydown" events instead of "keypress", instead of just seeing an event for Enter, you see one for Shift, then one for Enter... So I guess that modifiers and "special keys" behave correctly, but letters/digits/"regular keys" are blocked until the Omnibox is focused.
,
Sep 29 2017
,
Sep 29 2017
,
Oct 26 2017
,
Nov 28 2017
Hello, Same issue with the keypress event. Zebra TC51, Android 6.0.1, Chrome mobile. We use keypress events to record keystroke simulated by the embedded scanner. This works well until we have to use an "input type text" to input text using the "virtual keyboard" of android. Then after leaving the "input type text", we don't receive keypress events simulated by the embedded scanner anymore. As indicated previously: Clicking the omnibox then focusing the page makes it works again. As a workaround, we currently use a input type text to record scanned barcodes. But this not a good solution because a useless "virtual keyboard" pops up...
,
Nov 28
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 18
,
Dec 20
amaralp@: This looks like a virtual-keyboard + focus issue. Any idea who owns this now?
,
Dec 20
changwan@ is probably the one with most experience with IME on Clank.
,
Dec 20
Is 'handheld barcode scanner' necessary for repro? I don't have any.
,
Dec 27
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by ppolise...@chromium.org
, Nov 4 2016