|
|
Descriptioncolor: Make images without embedded profiles sRGB by default
This is only under the --enable-color-correct-rendering flag.
BUG=44872
Committed: https://crrev.com/1614d49c8ff84f43b6d5abdfa6e78beec18101c4
Cr-Commit-Position: refs/heads/master@{#420157}
Patch Set 1 #
Total comments: 3
Patch Set 2 : Use DCHECK #Messages
Total messages: 20 (8 generated)
ccameron@chromium.org changed reviewers: + scroggo@chromium.org
I somehow missed this my first time through adding SkColorSpaces to decoded images...
scroggo@google.com changed reviewers: + msarett@chromium.org, scroggo@google.com
lgtm
msarett@google.com changed reviewers: + msarett@google.com
https://codereview.chromium.org/2359643002/diff/1/third_party/WebKit/Source/p... File third_party/WebKit/Source/platform/image-decoders/ImageFrame.cpp (right): https://codereview.chromium.org/2359643002/diff/1/third_party/WebKit/Source/p... third_party/WebKit/Source/platform/image-decoders/ImageFrame.cpp:109: colorSpace = SkColorSpace::NewICC(newIccProfile.data(), newIccProfile.size()); NewICC() might fail (return nullptr) - if the input data is bad or if the profile is one that we don't yet recognize. Should we set also set the colorSpace to sRGB if NewICC() returns nullptr?
Thanks! https://codereview.chromium.org/2359643002/diff/1/third_party/WebKit/Source/p... File third_party/WebKit/Source/platform/image-decoders/ImageFrame.cpp (right): https://codereview.chromium.org/2359643002/diff/1/third_party/WebKit/Source/p... third_party/WebKit/Source/platform/image-decoders/ImageFrame.cpp:109: colorSpace = SkColorSpace::NewICC(newIccProfile.data(), newIccProfile.size()); On 2016/09/21 12:06:40, msarett wrote: > NewICC() might fail (return nullptr) - if the input data is bad or if the > profile is one that we don't yet recognize. Should we set also set the > colorSpace to sRGB if NewICC() returns nullptr? I was considering to add an ASSERT for that, rather than silently failing. This is still behind a flag, so the more landmines the better IMO. Changed this to an ASSERT.
The CQ bit was checked by ccameron@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from scroggo@google.com Link to the patchset: https://codereview.chromium.org/2359643002/#ps20001 (title: "Use DCHECK")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
https://codereview.chromium.org/2359643002/diff/1/third_party/WebKit/Source/p... File third_party/WebKit/Source/platform/image-decoders/ImageFrame.cpp (right): https://codereview.chromium.org/2359643002/diff/1/third_party/WebKit/Source/p... third_party/WebKit/Source/platform/image-decoders/ImageFrame.cpp:109: colorSpace = SkColorSpace::NewICC(newIccProfile.data(), newIccProfile.size()); On 2016/09/21 18:23:02, ccameron wrote: > On 2016/09/21 12:06:40, msarett wrote: > > NewICC() might fail (return nullptr) - if the input data is bad or if the > > profile is one that we don't yet recognize. Should we set also set the > > colorSpace to sRGB if NewICC() returns nullptr? > > I was considering to add an ASSERT for that, rather than silently failing. This > is still behind a flag, so the more landmines the better IMO. > > Changed this to an ASSERT. ASSERT seems good for now - especially if it helps us recognize profiles that we aren't parsing correctly. I would love to see those :). When this gets turned on, we'll obviously need to do something different (I think setting to sRGB makes sense). There certainly are images on the web that say they have ICC profiles and then give us garabage...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
On 2016/09/21 18:34:22, commit-bot: I haz the power wrote: > Try jobs failed on following builders: > chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, > http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...) scroggo, could you lgtm from your @chromium.org account?
On 2016/09/21 19:43:22, ccameron wrote: > On 2016/09/21 18:34:22, commit-bot: I haz the power wrote: > > Try jobs failed on following builders: > > chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, > > > http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...) > > scroggo, could you lgtm from your @chromium.org account? D'oh! LGTM, too!
The CQ bit was checked by ccameron@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== color: Make images without embedded profiles sRGB by default This is only under the --enable-color-correct-rendering flag. BUG=44872 ========== to ========== color: Make images without embedded profiles sRGB by default This is only under the --enable-color-correct-rendering flag. BUG=44872 Committed: https://crrev.com/1614d49c8ff84f43b6d5abdfa6e78beec18101c4 Cr-Commit-Position: refs/heads/master@{#420157} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/1614d49c8ff84f43b6d5abdfa6e78beec18101c4 Cr-Commit-Position: refs/heads/master@{#420157} |