New issue
Advanced search Search tips

Issue 899159 link

Starred by 1 user
Status: WontFix
Owner:
ellyjo...@chromium.org
Closed: Oct 29
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:'Reload' ,'Back Navigation' ,'Forward Navigation' buttons are seen Faint in chrome chip.

Reported by shruti.j...@etouch.net, Oct 26 
Chrome Version:72.0.3591.0 (Official Build) Revision148434e1b31c81381aec3e1346c9bf7954de39d6-refs/branch-heads/3591@{#1}(64-bit)
OS: MAC(10.13.1,10.13.6,10.14.1)

What steps will reproduce the problem?
(1) Launch chrome and navigate to chrome://version,chrome://extensions page.
(2) Click on chrome chip and observe the buttons.

Actual Result:'Reload' ,'Back Navigation' ,'Forward Navigation' buttons are seen Faint in chrome chip.
Expected Result: 'Reload' ,'Back Navigation' ,'Forward Navigation' buttons should be seen black in chrome chip.

This is a regression issue, broken in 'M72', and below is bisect info:
Good Build:72.0.3583.0
Bad Build:72.0.3584.0

Chromium bisect info:

You are probably looking for a change made after 600223 (known good), but no later than 600228 (first known bad).

CHANGE-LOG URL:
  
https://chromium.googlesource.com/chromium/src/+log/62f2f8f209a82db0dd5a311eb4f844bddb75c98e..631a939b2b9a02a05cd1db367c7ea7fb17d14f50

Suspecting: https://chromium.googlesource.com/chromium/src/+/177774d57a744b75630cba5507c3bf1ed419aea3

@dpapad: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Note:
1.Tried per revision bisect on Windows ,Mac and Linux OS but unable to perform the same since getting "RuntimeError: We don't have enough builds to bisect" error 
2.Hence provided suspect through 'Chromium bisect'
3.Issue not seen on: Windows(7,8,8.1,10) and Linux(14.04 LTS) OS


Thank You
Actual_result.mov
5.1 MB View Download
Expected_result.mov
5.7 MB View Download

Comment 1 by dpa...@chromium.org, Oct 26

Cc: dpa...@chromium.org
Owner: ericrk@chromium.org
r600225 only affects WebUI surfaces, and the problem here is occuring in native (non-WebUI) surfaces.

@ericrk: Could this be related to your CL at r600227 ?

Comment 2 by ericrk@chromium.org, Oct 26

Owner: ellyjo...@chromium.org
I re-bisected and ended up with a different range:
https://chromium.googlesource.com/chromium/src/+log/e28b88d0dc4b570f2c1908445501648f12f9198c..745d385ecf5ac39ca2fd604dd5451e61e47d980b

Looking at this range, it seems likely that this was an intentional UI change, see this CL:
"views: fade buttons in inactive widgets" - https://chromium.googlesource.com/chromium/src/+/821bb5d7ee96d2ce476850875e3a6459a5528d64

ellyjones@ can you confirm that this is working as intended?

Comment 3 by ellyjo...@chromium.org, Oct 29

Status: WontFix (was: Assigned)
That looks WAI to me - there is another window up (the info chip) so the browser's window is inactive.
►

Sign in to add a comment