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

Issue 862061 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: [Win-10 custom titlebar] Selected color doesn't get effected to window title bar.

Reported by dchau...@etouch.net, Jul 10

Issue description

Chrome Version: 69.0.3487.0 (Official Build) Revision	5c3042df84f213c3e25cf3d2aceede00fa994ef3-refs/branch-heads/3487@{#1} 32/64-bit
OS: Windows-10

Precondition:
1. Enable "windows10-custom-titlebar" in chrome://flags
2. Setup:
    A. Open Windows machine settings > Personalization > Colors
    B. 'Enable (On) 'Show Color on Title bar
    C. Select any required color from 'Accent colors'.

What steps will reproduce the problem?
1. Open latest Chrome canary and observe.

Actual: Selected color doesn't get displayed on window title bar.
Expected: Selected color should get displayed on window title bar.

This is a regression issue broken in M-69 series, will soon update other info.
 
Labels: Needs-Feedback
Can't repro; Chrome has code to obey this color and that code seems to be working AFAICT.

Did you fully restart Chrome after changing your accent color?

Are you using MD refresh?  If so, did you open more than one tab?  With only one tab open, the frame is always white, and that's by design.
Cc: pkasting@chromium.org
Labels: -Needs-Feedback
With response to comment #1: 
Yes, we relaunch the Chrome after changing accent color.

This issue is only reproducible on MD refresh. On opening the second tab, selected color get effected on window title bar.

Kindly review the attached screen-cast for reference.

Thank you.
Actual behavior.mp4
2.8 MB View Download
Expected behavior.mp4
2.7 MB View Download
Labels: hasbisect
Owner: kylixrd@chromium.org
Status: Assigned (was: Unconfirmed)
Below is manual regression range:

Good build: 69.0.3472.0 (Revision: 569949)
Bad build: 69.0.3473.0 (Revision: 570288)

Unable to provide the bisect using has-bisect-per-revision script. Hence providing the bisect using old script:
CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/3c16d9d466102e0839cad4e70cea850107143ca4..64c540a750df6adb453c0f8e6e63800d8948d04c?pretty=fuller&n=100

Suspecting: https://chromium.googlesource.com/chromium/src/+/8a4187003e401bcb6a541427fe72fc425c5a9f1b

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

NOTE: 
1. This issue is not reproducible on Windows(7,8,8.1), Mac(10.12.6 , 10.13.1 , 10.13.6, 10.14) and Linux(14.04) OS.
2. This issue is also reproducible on Dev #69.0.3472.3

Thank you.
Status: WontFix (was: Assigned)
It sounds like what you're reporting is that with a single tab open, the frame is white.

From comment 1: "With only one tab open, the frame is always white, and that's by design."
Cc: groby@chromium.org bettes@chromium.org markchang@chromium.org
Labels: Proj-MdRefresh

Sign in to add a comment