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

Issue 688915 link

Starred by 1 user
Status: WontFix
Owner:
dpa...@chromium.org
Closed: Feb 2017
Cc:
█ hdodda@chromium.org
nyerramilli@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression: In chrome://md-settings/searchEngines, input container does not turn red on clearing search engine name.

Reported by lpa...@etouch.net, Feb 6 2017 
Chrome Version: 58.0.3004.0 (Official Build) 604a36b20d9ffe65380031f3f708d859d81f71be-refs/heads/master@{#448183} (32/64-bit)
OS: Windows (7,8,10), Mac (10.11.6, 10.12.1), Linux (14.04 LTS)

What steps will reproduce the problem?
1) Launch chrome, go to chrome://md-settings/searchEngines and click on iron icon for Google search engine.
2) Select Edit, clear Search engine name and observe.

On clearing Search engine name, input container should turn red.

On clearing Search engine name, input container does not turn red.

This is a Regression issue broken in M-55, will soon update other info
Manual bisect:
Good build: 55.0.2869.0
Bad build: 55.0.2871.0
search_actual.mp4
407 KB View Download
search_expected.mp4
339 KB View Download

Comment 1 by hdodda@chromium.org, Feb 6 2017

Cc: hdodda@chromium.org
Labels: hasbisect-per-revision
Owner: dpa...@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build: 55.0.2869.0 (revision : 420536)
Bad build: 55.0.2871.0 (revision : 420831)

You are probably looking for a change made after 420669 (known good), but no later than 420670 (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/00d1ed465088e90594ca2c0858e5f2d13d5a3526..033d1f2ef2f8e4124eca1c7de9db5a42e58c4601

From the CL above, assigning the issue to the concern owner 

@dpapad - 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.

Review-Url: https://codereview.chromium.org/2366783002

Thanks!

Comment 2 by dpa...@chromium.org, Feb 6 2017

Labels: -Pri-1 Proj-MaterialDesign-WebUI Pri-2

Comment 3 by dbeam@chromium.org, Feb 7 2017

Labels: -M-58 Hotlist-MD-Settings-SearchEngines

Comment 4 by dpa...@chromium.org, Feb 9 2017

Status: WontFix (was: Assigned)
This is WAI. The behavior was changed on purpose, such that the user does not see  unnecessary invalid warnings, by just tabbing through the 3 input fields. Notice that even though the red warning message is not shown for empty input fields, the "add/edit" button is disabled.

See more details at https://bugs.chromium.org/p/chromium/issues/detail?id=621456.
►

Sign in to add a comment