New issue
Advanced search Search tips

Issue 714607 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 2
Type: Bug-Regression



Sign in to add a comment

GLIF icon is not displayed for queries in voice search and results containing TTS are not spoken on SRP

Project Member Reported by rakurati@chromium.org, Apr 24 2017

Issue description

App Version: 58.0.3029.87
iOS Version: 10.2.1, 10.3.2 beta
Device: iPhone 7 plus, iPhone6 plus

Precondition:
Settings -> Voice Search -> Turn ‘ON’ Speak Answers Back
Settings ->Search Engine -> ‘Google’

Steps to reproduce:
1. Launch chrome and tap on the voice search
2. Search for query like “What is time?” or “what day it is?”

Observed results: 
1. Notice results page not displayed any GLIF icon.
2. Notice the results containing TTS are not spoken.

Note: If voice search query is some website url (amazon.com) then result page displays GLIF icon.

Expected results:
The voice search query result page should display the GLIF icon.

Number of times you were able to reproduce: 5/5
Bug reproducible after clean install: Yes
Bug reproducible after clearing cache and cookies: Yes
Bug reproducible on Chrome Mobile on Android: No
Bug reproducible on Firefox/Safari: Firefox: NA, Safari: NA
Bug reproducible on current stable build (App Version, iOS Version): Yes on M57
Bug reproducible on the current beta channel build (App Version, iOS Version): Yes on M58

Link to video/image: https://drive.google.com/a/google.com/file/d/0B8Cek8RsDbF8WmN6M0hqR1VMLVE/view?usp=sharing

 
Issue is also noticed on iPad's

Comment 2 by sczs@chromium.org, May 3 2017

Labels: M-60
Owner: kkhorimoto@chromium.org
Status: Assigned (was: Untriaged)
kkhorimoto@ could you please take a look
Cc: linds...@chromium.org
Summary: GLIF icon is not displayed for queries in voice search and results containing TTS are not spoken on SRP (was: GLIF icon is not displayed for queries in voice search results page)
Labels: -Type-Bug -M-60 ReleaseBlock-Stable M-59 Type-Bug-Regression
This is a regression. Voice Search is not speaking the answers back for any of the basic queries. Ex: Who is the president, What is the time now etc.
This was working fine in M56.0.2924.79 version of stable release.
Cc: kkhorimoto@chromium.org
Owner: srikanthg@chromium.org
Status: Started (was: Assigned)
This doesn't reproduce on the latest canary; is it still occurring on the M59 branch?  If so, could we bisect when this bug stopped occurring in canary to narrow down my search for which CL needs to be cherry-picked?
Cc: -kkhorimoto@chromium.org srikanthg@chromium.org
Owner: kkhorimoto@chromium.org
I can still reproduce this on M60.0.3095.0 canary.
I tried with existing app and with Fresh installation as well.
GLIF voice search is not speaking answers at all.

Tested on devices with English, US locale, iOS10.3.2, 10.1.1, iPhone7 plus and iPhone6.

Few of us from test team noticed that it worked very rarely and then stopped again. Can you try with a fresh installation of canary?
I've tried with the latest canary (60.0.3096.0) and also ToT on my iPhone 6s iOS 10.3.2, but have not been able to reproduce.  I'll try using some other devices to see if I can repro it there.

I should note that on a previous version of canary, I was able to reproduce this consistently on my phone; I just haven't been able to do it with the later versions.
Also couldn't repro with our iPhone 7 Plus on iOS 10.0.2
I also attempted reproducing on 58.0.3029.87, but text-to-speech worked fine for me there as well.
srikanthg@ is this bug happening in M59?
We (anyone in test team) not able to reproduce this issue on any of our devices. This was failing very consistently across all of our devices in the past few weeks. In the past weeks we have this issue where google.com is redirecting to google.com/#spf=1 and is there any chance this issue is related to that?
I have no way to confirm.

As of today: This issue is no longer reproduced on any devices, any chrome version any iOS.
Status: WontFix (was: Started)
I don't think the redirect issue would have an effect here, but I haven't been able to reproduce so I can't be sure about why it was happening.  It's possible that this was introduced/fixed by some unrelated refactoring around the WebStateList implementation.  I'm going to mark as WontFix; please reopen with more details if this starts to occur again.  Thanks!

Sign in to add a comment