Issue metadata
Sign in to add a comment
|
Color correct rendering leaving blocks of incorrect colours
Reported by
tho...@3whitehats.com,
Oct 4 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Example URL: https://www.3whitehats.com/ Steps to reproduce the problem: 1. Visit the website 2. 3. What is the expected behavior? That elements with a background colour have a consistent background colour, and that it isn't changed for random blocks in the same element. What went wrong? Inconsistent colour rendering, even within the same element. Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? Yes I want to say 60 Does this work in other browsers? Yes Chrome version: 61.0.3163.100 Channel: stable OS Version: 10.0 Flash Version: We're perfectly happy if the colour is rendered differently for different colour profiles, but it needs to be done consistently so every instance of the colour is displaying the same.
,
Oct 5 2017
Able to reproduce this issue on 60.0.3112.113 , on latest canary 63.0.3231.0 using Mac 10.12.6, Windows 10 and Ubuntu 14.04 with steps mentioned in comment#0. Manual Bisect Info: ================ Good Build: 61.0.3143.0 Bad Build: 61.0.3144.0 You are probably looking for a change made after 482903 (known good), but no later than 482904 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/8b4643f67dc1c6b142a152aa2b76c771287e3a22..1894d423068be735560e0171922c833c4091b5d1 Reviewed-on: https://chromium-review.googlesource.com/551092 Suspecting same from changelog. @ccameron: Please confirm the bug and help in re-assigning if it is not related to your change. Adding RB-Stable as this is recent regression. Please change if not the case Thanks!
,
Oct 5 2017
This is probably a dupe of the issue I reported: https://bugs.chromium.org/p/chromium/issues/detail?id=771006 The bisection itself is inconclusive, please check my issue to undertstand why. The issue shows itself since when color correction is enabled by default (which is the commit you found) but the problem itself should be in another commit. Is there a way to merge this report to mine to avoid confusion? Jack
,
Oct 5 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Oct 5 2017