Regression: Red underline is seen on autofill page even after entire text is erased.
Reported by
db...@etouch.net,
Jun 27 2018
|
||||
Issue descriptionChrome Version :68.0.3440.42 Revision:1e775812933cd8759b2ac69a967b17767d3063bd-refs/branch-heads/3440@{#544} (32/64 bit) OS: Win (7,8,8.1,10), Mac OS X (10.12.6,10.13.1,10.13.6), Linux (14.04 LTS). Steps to reproduce: 1. Launch Chrome, Navigate to chrome://settings/autofill and zoom the page to 150%. 2. Click 'Add' button against 'Address' label and Enter any random text in 'Name' field. 3. Select that text, drag and drop it to 'Street' field. 4. Now delete the text using 'Backspace' and observe. Actual: Red underline is seen even after entire text is erased. Expected: Red underline should disappear once the text is erased. This is regression issue broken in ‘M-67’ and below is the has-bisect per-revision info: Good Build: 67.0.3371.0 (Revision: 543279) Bad Build: 67.0.3372.0 (Revision: 543592) You are probably looking for a change made after 543290 (known good), but no later than 543291 (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/63667eca2a1d86f5de61f29c7c5c6417cc351757..3a3c78a924a686ed0d3f90d765b00cdd78453e11 Suspecting: https://chromium.googlesource.com/chromium/src/+/3a3c78a924a686ed0d3f90d765b00cdd78453e11 wangxianzhu@: Could you please help to reassign if your change is not the cause for this change. Note: Issue is also seen on Stable build #67.0.3396.99, Dev build #69.0.3472.3 and Canary build #69.0.3474.0 Thank You!
,
Jun 27 2018
This is not a P1 because the failed validation gets corrected sooner or later and this doesn't affect usability. I reported this issue a while back, so it's not new. We are simply failing to account for zoom when setting the invalidation rect for markers.
,
Jul 3
I will be on vacation for 1 month. trchen@ any chance to look at this bug before I'm back?
,
Sep 14
I'm leaving the team, thus re-assigning. |
||||
►
Sign in to add a comment |
||||
Comment 1 by schenney@chromium.org
, Jun 27 2018