New issue
Advanced search Search tips

Issue 781229 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 3
Type: Bug



Sign in to add a comment

Auto correct text of description is not fetched into Report an issue preview

Project Member Reported by rakurati@chromium.org, Nov 3 2017

Issue description

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

Precondition: 
Device keyboard>>Auto correction should be enabled

Steps to reproduce:
1. Launch chrome
2. Open Report an issue window
3. Enter text with incorrect spell in Description (eg: Himalyas)
4. Dismiss the keyboard and tap on next button

Observed results:
Notice that on dismiss of keyboard the text in description gets auto correct (to Himalayas) but the text in preview is displaying the user input text.

Expected results:
If the user input text gets auto corrected then the same text should reflect in description

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 M62
Bug reproducible on the current beta channel build (App Version, iOS Version): Yes on M63

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

 
Cc: sdefresne@chromium.org
Cc: pkl@chromium.org
Hi Peter, do you know who is working on feedback kit?
Owner: sdefresne@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by pkl@chromium.org, Nov 10 2017

Owner: peterlaurens@chromium.org
peterlaurens@ is working on upgrading FeedbackKit. The bug may be inside FeedbackKit instead of something that Chrome controls. This does not seem like a new issue though.
Issue reproduces with the FeedbackKit 2.0 flag flipped. Presumably an event ordering problem (may not be trivial to fix).
Owner: ----

Sign in to add a comment