[TTS] Address recognition doesn't select the full address |
||||
Issue descriptionWith Quick Actions we recognize addresses, but Tommy just showed me a case where we don't expand the selection to select the full address (which is confusing). I thought we'd already landed a server-side change to fully extend the selection to include the recognized coca action text range, but maybe there's a bug there.
,
Feb 27 2017
I found an example where we expand too far after coca recognizes a URL. The intent we get back is correct and navigates to the expected URL but the selection and display text are incorrect if I tap on most parts of the URL. If I tap toward the start of the URL on "http" or "www" then the selection is correct. "http://www.example.com/index.html" on https://en.wikipedia.org/wiki/Uniform_Resource_Locator
,
Feb 27 2017
,
Feb 27 2017
,
Mar 7 2017
There are actually two different bugs here: The first has a selection that's too short due to Coca not returning a content-reference for the whole address. I'll filed a Coca bug for this (at https://b.corp.google.com/issues/36006993). The second is due to our GWS plugin trying to find a content-reference that includes the whole search term we've determined, but in these cases it's too long. I think we should instead find a content-reference that just includes the original selection. https://b.corp.google.com/issues/36008206. I'll send out a CL to make that change.
,
Mar 7 2018
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. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 7 2018
Addressed with server-side bugs. |
||||
►
Sign in to add a comment |
||||
Comment 1 by donnd@chromium.org
, Feb 27 2017