Using GBoard swipe in omnibox doesn't trigger "Go" button and add space |
|||||||
Issue descriptionChrome Version: 57.0.2987.137 OS: iOS What steps will reproduce the problem? (1) Use GBoard (2) Tap into omnibox (3) Type any word using swipe gesture (4) Type another word using swipe gesture What is the expected result? After swiping first word, have "Go" button on keyboard be highlighted blue and clickable. After swiping second word, see a space in between first and second word. What happens instead? After swiping first word, "Go" is disabled. I have to type a space to be able to navigate. After swiping second word, the first and second words are joined up together without any spaces in between. Note: This works fine in Safari though I'm not sure if it's a Chrome bug or a GBoard bug.
,
Apr 11 2017
Thanks for looking into it. If it helps, I'm using the latest version of GBoard: 1.3.1
,
Apr 11 2017
I am using the Gboard version that comes with iGSA Stable. Version 24.1.151204851
,
Apr 12 2017
Srikanth can you please check for repro and report gBoard version if reproducible?
,
Apr 12 2017
This is a WNF based on http://b/28982336 Steps to repro from the original bug: 1. Go to a chrome tab you already have results on 2. Tap on address bar 3. Type a search using the swipe typing (e.g. "amtrack") 4. The "Go" button is greyed out so you can't make a search (you can press space bar and then it works) ktam@ are you seeing this behavior on NewTabPage or on a tab that already has some webpage loaded.
,
Apr 12 2017
btw., I am able to reproduce based on the steps from comment#5 using GBoard Version 1.3.1 on Chrome M57,59. Same steps works fine on Safari. Firefox: Go button is enabled on first swipe, but there is no space added when you swipe for the second time.
,
Apr 12 2017
I'm not seeing this behavior on the New Tab Page. Only on tabs with pages I've already loaded. What was the reason for it being marked as WNF? I assume this is not intended behavior?
,
Apr 12 2017
So I am able to reproduce this now with both versions of the GBoard. The one that comes with iGSA and the stand-alone one (V1.3.1). This happens only the first time the keyboard is invoked. If you hit space (so the Go button is enabled) then delete all and try swipe-type again, the Go button is no longer grey. ktam@ : I commented on the buganizer bug that Srikanth linked to.
,
Jun 27 2017
This sounds like a noticeable issue. Should Chrome for iOS fix it, or does someone need to push on that gboard bug that's closed as WillNotFix? (I think the gboard team is likely ignoring it given that it's closed...)
,
Jun 28 2017
+ Rohit, Justin I think this should be fixed. There are some other (and probably higher priority) GBoard/Bling Omnibox bugs that we're working through as well with the GBoard team. i.e. https://b.corp.google.com/issues/36646068 https://b.corp.google.com/issues/62494463
,
Jun 28 2017
komatsu@ What is gBoard looking at to disable the 'go' button? The text replacement seems to work, the state looks correct on our side. Other keyboards that do swipe (word flow, swype, etc) seem to work correctly?
,
Jun 11 2018
The assigned owner "komatsu@chromium.org" is not able to receive e-mails, please re-triage. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 13 2018
Should've been marked as Fixed at the time. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by mard...@chromium.org
, Apr 11 2017