New issue
Advanced search Search tips

Issue 797750 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

Voice over reads invalid text on entering first text in the description field of Report an issue

Project Member Reported by rakurati@chromium.org, Dec 27 2017

Issue description

App Version: 64.0.3282.55 Beta
iOS Version: 10.3.3, 11.2
Device: iPhone and iPad

Steps to reproduce:
1. Turn on device voice over
2. Launch chrome and open report an issue tab
3. Select description and double tap 
4. Enter any first character

Observed results:
On entering first character an invalid or non related text like descriptioo is being read out by voice over.

Expected results:
Valid info/display text should be only read by voice over.

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: Not tested
Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA
Bug reproducible on current stable build (App Version, iOS Version): Yes on M63
Bug reproducible on the current beta channel build (App Version, iOS Version): Yes on M64 Beta

Link to video/image:
https://drive.google.com/file/d/1Ftp6gQcIQNtdTr6atUg5opazLOyoJT-s/view?usp=sharing

 
Owner: sdefresne@chromium.org
Status: Assigned (was: Untriaged)
Owner: pkl@chromium.org
pkl: should we still fix this or close as WontFix given the move the new version of "Report an issue" UI?

Comment 3 by pkl@chromium.org, Mar 21 2018

Cc: pkl@chromium.org
Owner: ----
Status: Available (was: Assigned)
Leave this as Available until new FeedbackKit is in place.
This issue is still happening in the new Feedback kit V2

Tested on 67.0.3396.32 Beta

Link to the video:
https://drive.google.com/file/d/1I0iod0diu-n2UHtC259Oa4yvlzIa5wrG/view?usp=sharing


Comment 5 by pkl@chromium.org, May 3 2018

Probably a problem within FeedbackKit and I should file a bug on that.

Sign in to add a comment