New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 868108 link

Starred by 2 users
Status: Started
Owner:
█ donnd@chromium.org
(OOO slow)
Cc:
twelling...@chromium.org
janicewong@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Feature



Sign in to add a comment

[TTS] Consider not disabling when Smart Text Selection is active

Project Member Reported by donnd@google.com, Jul 26 
Tap to Search doesn't trigger on recent Android versions, and this is a point of some confusion for users.  We should consider triggering along with Smart Selection instead, by default.

I think there's already a bug for this, but couldn't find it...

Comment 1 by donnd@google.com, Jul 26

Components: UI>Browser>Search>ContextualSearch

Comment 2 by donnd@google.com, Aug 21

Labels: -Target-70 Target-71
Another idea is to detect whether Smart Select has activated or not, and show the TTS Bar any time it did not activate.

Comment 3 by karemani...@gmail.com, Sep 20 

Hi,

Is there any update on this issue further ?

Thanks,
Smita

Comment 4 by donnd@google.com, Sep 20

Labels: -Target-71
Won't be done this cycle, removing target milestone.

Comment 5 by donnd@google.com, Nov 14

Cc: twelling...@chromium.org janicewong@chromium.org
Labels: Target-72
Status: Started (was: Assigned)
Janice, do you have any objection to me starting work on this?  

I think the fact that we suppress TTS when Smart Selection *might* be active or give an answer is more confusing than just always allowing TTS to trigger.  I think we should do an experiment in M-72 but don't know offhand what our success criteria should be.  Do you think we need to track usage of Smart Selection?
►

Sign in to add a comment