aboutsummaryrefslogtreecommitdiffhomepage
path: root/include
diff options
context:
space:
mode:
authorGravatar msarett <msarett@google.com>2016-08-22 09:44:35 -0700
committerGravatar Commit bot <commit-bot@chromium.org>2016-08-22 09:44:35 -0700
commit0f0c4f0902af265b74f4f679556e375e0ed8d944 (patch)
tree3372d3981a073eb79abbdf9687889899875ac3b9 /include
parenta61b6d4f9e8ce7134414c84cec075482c2f8efcc (diff)
Detect all named gammas
Our DstColorSpace UMA is showing some named gammas that are not appropriately detected and placed in named categories. https://uma.googleplex.com/p/chrome/histograms?endDate=latest&dayCount=1&histograms=Blink.ColorSpace.Destination&fixupData=true&showMax=true&filters=isofficial%2Ceq%2CTrue&implicitFilters=isofficial This CL should fix that. I'm not sure (yet) how I feel about this landing permanently. Seems a little messy. But it will be interesting to see how this affects the UMA. My best guess is that we are hitting this case when all three gammas are "invalid" in different ways. I'm expecting to see some profiles end up in the "invalid" category now. It's also possible that we'll see these cases being absorbed into sRGB or somewhere else. BUG=skia:5656 GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2261213002 Review-Url: https://codereview.chromium.org/2261213002
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions