New issue
Advanced search Search tips

Issue 762491 link

Starred by 2 users
Status: Duplicate
Merged: issue 755747
Owner:
ccameron@chromium.org
Closed: Sep 2017
Cc:
pbomm...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome 61 uses incorrect color profile

Reported by spry...@gmail.com, Sep 6 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36

Steps to reproduce the problem:
1. Set the page background color to pure red
2. Take a screenshot and compare it with 100% red in Photoshop
3. It's more desaturated now. Picture: https://bot.gyazo.com/834813ec6dd6205455fe04d7d98a9c08.png

What is the expected behavior?
Should be using the correct color profile (that v60 used)

What went wrong?
It's now using the incorrect color profile

Did this work before? Yes 60

Chrome version: 61.0.3163.79  Channel: stable
OS Version: OS X 10.12.6
Flash Version:

Comment 1 by pbomm...@chromium.org, Sep 6 2017

Cc: pbomm...@chromium.org
Components: Internals>GPU
Labels: M-61
Owner: ccameron@chromium.org
Status: Assigned (was: Unconfirmed)
ccameron@ can you please take a look assuming this is related to  issue#713889

Comment 2 by ccameron@chromium.org, Sep 6 2017

Mergedinto: 755747
Status: Duplicate (was: Assigned)
Chrome 61 is now respecting the color profile that has been selected on your machine?

What color profile are you using on this machine?

If you are not using an sRGB color profile, then it is not expected that #FF0000 will appear as the RGB value (1,0,0) on your machine. Chrome 60 incorrectly did that, but it has been fixed in Chrome 61.

If you want this behavior, then go to System Preferences -> Displays -> Color, and select the "sRGB IEC61966-2.1" profile (see the attached screenshot).

Duping this to "users have color profile that they don't want respected".
Screen Shot 2017-09-06 at 10.11.19 AM.png
92.2 KB View Download
►

Sign in to add a comment