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

Issue 657381 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression:Grey highlight is not seen after selecting "Move down" option in chrome://md-settings/languages

Reported by adha...@etouch.net, Oct 19 2016

Issue description

Chrome Version: 56.0.2895.0 d9d3ea15202868716617ceb73ee8d5595778d504-refs/heads/master@{#426105} (32/64 bit)
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.10.5, 10.11.4)

Pre-condition:Please make sure to add 2-3 languages.

What steps will reproduce the problem?
(1)Launch Chrome and navigate to chrome://settings/advanced
(2)Click on 'Add languages' under language section and add 3-4 languages.(Kindly refer the video)
(3)Click on the iron icon of the any language.(Kindly refer the video)
(4)Select "Move down" option and observe.

Actual:Grey highlight is not seen after selecting "Move down" option.

Expected:Grey highlight should be seen after selecting "Move down" option.

This is a Regression issue broken in M-56,will soon update other info.

Good build:56.0.2891.0
Bad build:56.0.2894.0

 
Actual focus.mp4
676 KB View Download
Expected focus.mp4
312 KB View Download

Comment 1 by hdodda@chromium.org, Oct 20 2016

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:56.0.2891.0 (Revision: 425529)
Bad build:56.0.2894.0 (Revision: 425838)

You are probably looking for a change made after 425533 (known good), but no later than 425534 (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/4dbb42fe4765527a3f0ed359caac5f3dce7b1440..46b5ca1056271d70ed5e264612aafe9fa948a2a4

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/2402553002

Thanks !

Comment 2 by dpa...@chromium.org, Oct 20 2016

Cc: dbeam@chromium.org
Labels: Proj-MaterialDesign-WebUI
Not sure if this is a bug necessarily. The native dialog behaves slightly differently in terms of where does the focus returns after it gets closed.

Adding @dbeam who has thought about this before.

Comment 3 by dpa...@chromium.org, Oct 25 2016

Cc: dpa...@chromium.org
 Issue 658684  has been merged into this issue.

Comment 4 by dbeam@chromium.org, Oct 25 2016

Status: WontFix (was: Assigned)
actual is saner, IMO

Sign in to add a comment