Omnibox removes URL autocompletion when pressing return key on physical keyboard |
||||
Issue descriptionFeature: Physical Keyboard Version: 54.0.2790.0 Android version: MOB30M Device: Nexus 9 with external Bluetooth hardware keyboard (original HTC nexus cover) What steps will reproduce the problem? (1) Use any keyboard to enter an URL into the Omnibox for which auto-completion is available. (2) For example, after you typed "bugs", the text field in the Omnibox might show "bugs.chromium.org" with ".chromium.org" selected. (3) Press the enter key of the physical keyboard. What is the expected output? The browser should load the entire URL that is displayed (bugs.chromium.org), like it does on desktop and like it does when pressing the "Go" button on the virtual keyboard. What do you see instead? The selected test ".chromium.org" is replaced (possibly with newline or with nothing?) and then the query is issued, so the browser loads the Google search results for "bugs". Possibly related: https://bugs.chromium.org/p/chromium/issues/detail?id=169917
,
Jul 7 2016
,
Jul 7 2016
assigning to tedchoc@ for investigation or triage. (He's done stuff with the omnibox and physical keyboards recently.)
,
Jul 15 2016
FYI, On Samsung devices by using Samsung Keyboard settings and connected an external BT KB, issue is not seen with mentioned steps.
,
Jul 18 2016
Hmm...that is quite surprising. I can't repro this on a Pixel C either. If you go to Android settings -> Languages & input, is there anything interesting going on in there? Any chance you have a different bluetooth keyboard to test with (wondering if it is device/keyboard specific)? What language is your device set to? What happens if you go to other text fields in Android? Does it do the same thing? In particular, the FIP behavior is very suspect. We are specifically handling the KEYCODE_ENTER key there, so I'm thinking we are getting some other oddball keycode.
,
Jul 19 2016
This is not reproducible anymore (but it was still reproducible right after Comment 4 was added by ajith.v@samsung.com, I double-checked then). In between comments 3 and 5, the device did a couple of updates (it is MOB30P now), I got the latest Chromium code (54.0.2798.0) and the "Google Keyboard" was updated (now 5.1.23.127065177-arm64-v8a). So any of these updates might have fixed the issue. I played around a bit and can't reproduce it anymore in Chrome or Chromium. I think this bug can be closed, thank you for your help!
,
Aug 4 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by pke@google.com
, Jul 7 2016