Issue metadata
Sign in to add a comment
|
Regression: Unnecessary text is selected in 'Scale' field after tapping on error message.
Reported by
db...@etouch.net,
Oct 3
|
||||||||||||||||||||||
Issue descriptionChrome Version: 71.0.3569.0 Revision fb87327b9e0a0a50c96e084943e5525c25f76fd1-refs/branch-heads/3569@{#1}(32/64 bit) OS: Windows(10) Touch device What steps will reproduce the problem? (1) Launch chrome, open NTP and give Print command using ctrl+P. (2) Click on 'More settings' to expand and click on 'Scale' field. (3) Type invalid text into scale field(error msg appers),now tap/touch on error message and Observe. Actual: Unnecessary text is selected in scale field after tapping on error message. Expected: No such a text selection should seen. This is a regression issue, broken in M-71 series, below is manual regression range: Good build: 71.0.3551.0 (Revision: 590851) Bad build: 71.0.3552.2 (Revision: 591210) Using the 'per-revision' script providing the bisect result: You are probably looking for a change made after 591108 (known good), but no later than 591109 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/974aa7b559b4361d7410479796becb0b933dc6a4..e73e92b7fbf4206ffdb20282ac73bcbed7cf910e Suspecting: https://chromium.googlesource.com/chromium/src/+/e73e92b7fbf4206ffdb20282ac73bcbed7cf910e @rbpotter: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. NOTE: 1.Issue is touch specific and not seen on Mac (10.12.6, 10.13.1, 10.13.6, 10.14), Win (7, 8, 8.1, 10) & Linux (14.04 LTS) 2.This issue is also reproducible on Dev build #71.0.3559.6 Kindly review the attached screen-cast for reference. Thank you.
,
Oct 5
This same behavior occurs in all cr-inputs, not just Print Preview. The bisect is not really identifying when the behavior changed, as it just identifies when Print Preview switched from a native input to cr-input. I redid the bisect using a cr-input that has been around for some time in chrome://settings/searchEngines (in the "Add" dialog) and got the following result: https://chromium.googlesource.com/chromium/src/+log/7863843fe3159bb57b9430cd4849fb33087cfed5..b8a3cffde9ef95e21bd72562a092dd18c0ccc595 It's almost definitely https://crrev.com/c/1217747. Based on the description (select on focus) it sounds like this may be working as intended. Assigning to stevenjb@ to confirm.
,
Oct 30
I can't repro this in 71.0.3578.8. It seems like a pretty minor artifact at worst. Given the general complexity of keyboard focus and selection issues, I'm going to close this one as WontFix. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rbpotter@chromium.org
, Oct 3