aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/core/SkColorSpace_ICC.cpp
diff options
context:
space:
mode:
authorGravatar msarett <msarett@google.com>2016-08-24 06:22:41 -0700
committerGravatar Commit bot <commit-bot@chromium.org>2016-08-24 06:22:41 -0700
commit3bf7509c3f68aefbe5f8b2ea5888319a71a91d2d (patch)
tree009826a9c9d6ed6724a82adc6827b0b245ec8f03 /src/core/SkColorSpace_ICC.cpp
parent8aeec39f1fedfdd3508365ff0548cc3f876f6a00 (diff)
Warn on bad rendering intents (instead of valid ones)
Diffstat (limited to 'src/core/SkColorSpace_ICC.cpp')
-rwxr-xr-xsrc/core/SkColorSpace_ICC.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/core/SkColorSpace_ICC.cpp b/src/core/SkColorSpace_ICC.cpp
index 92dcc0fcf5..88fd1b345b 100755
--- a/src/core/SkColorSpace_ICC.cpp
+++ b/src/core/SkColorSpace_ICC.cpp
@@ -138,7 +138,7 @@ struct ICCProfileHeader {
// Should we treat different rendering intents differently?
// Valid rendering intents include kPerceptual (0), kRelative (1),
// kSaturation (2), and kAbsolute (3).
- if (fRenderingIntent <= 3) {
+ if (fRenderingIntent > 3) {
// Warn rather than fail here. Occasionally, we see perfectly
// normal profiles with wacky rendering intents.
SkColorSpacePrintf("Warning, bad rendering intent.\n");