New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 873608 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression: [NTP] Suggestion list doesn't appear on clicking 'Name/URL' text-box on 'Add shortcut' overlay.

Reported by dchau...@etouch.net, Aug 13

Issue description

Chrome Version: 70.0.3521.0 (Official Build) Revision	96b3e88306e2a71a9e1f4c77a79e39f597c199b9-refs/branch-heads/3521@{#1} (32/64-bit)
OS: Windows(7,8,8.1,10), Mac(10.12.6, 10.13.1, 10.14, 10.13.6) and Linux(14.04 LTs)

Pre-condition: Enable "Enable using the Google local NTP" and "New Tab Page Custom Links" flags from chrome://flags.

What steps will reproduce the problem?
1. Launch Chrome and navigate to NTP.
2. Click on 'Add shortcut' icon and add the shortcut. 
3. Again navigate to 'Add shortcut' overlay, click on 'Name' text-box and observe.

Actual: Suggestion list doesn't appear on clicking 'Name/URL' text-box.
Expected: Suggestion list should appear on clicking 'Name/URL' text-box.

This is a regression issue, broken in M-70 series, below is manual regression range:

Good build: 70.0.3514.0 (Revision: 580791)
Bad build: 70.0.3515.0 (Revision: 581084)

Using the 'per-revision' script providing the bisect result:

You are probably looking for a change made after 580948 (known good), but no later than 580949 (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/631ac11aae294abc8b5a100a09e59af59aa6e229..c2111e0695751dcd6833f86930ea7905daef9494

Suspecting: https://chromium.googlesource.com/chromium/src/+/c2111e0695751dcd6833f86930ea7905daef9494

@kristipark: 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.

Kindly review the attached screen-cast for reference.

Thank you.
 
Actual behavior.mp4
560 KB View Download
Expected behavior.mp4
540 KB View Download
Cc: yyushkina@chromium.org
Labels: -Pri-1 Pri-3
Thanks for your report!

I think autocomplete=off was required to support some accessibility requirements (Kristi to confirm).

In any case, lowering the priority of this bug, since it's nice to have (if we can support it), but not essential. 
Yes, autocomplete=off was an accessibility requirement.
Status: WontFix (was: Assigned)
Given on Kristi's confirmation, marking this WontFix.

Sign in to add a comment