Refactor image decoders to use 'colorSpace' instead of 'colorProfile'

third_party/WebKit/Source/platform/graphics/DeferredImageDecoder.cpp

Index: third_party/WebKit/Source/platform/graphics/DeferredImageDecoder.cpp
diff --git a/third_party/WebKit/Source/platform/graphics/DeferredImageDecoder.cpp b/third_party/WebKit/Source/platform/graphics/DeferredImageDecoder.cpp
index f537818dff763662ffd2626a2e65aaead7bcadd2..4d57e7b123176fc61ab947c137feacd3d11376a6 100644
--- a/third_party/WebKit/Source/platform/graphics/DeferredImageDecoder.cpp
+++ b/third_party/WebKit/Source/platform/graphics/DeferredImageDecoder.cpp
@@ -180,8 +180,7 @@ bool DeferredImageDecoder::isSizeAvailable() {
 }
 
 bool DeferredImageDecoder::hasColorProfile() const {
-  return m_actualDecoder ? m_actualDecoder->hasColorProfile()
-                         : m_hasColorProfile;
+  return m_actualDecoder ? m_actualDecoder->hasColorSpace() : m_hasColorProfile;

[f(malita), 2016/10/27 15:57:28]

If we're renaming ImageDecoder::hasColorProfile -> hasColorSpace, would it make
sense to also rename DeferredImageDecoder::hasColorProfile?

[msarett, 2016/10/27 16:42:56]

Yeah I think so.  In general, it probably makes sense to push the profile->space
change outside of the decoders (which I was avoiding a little bit).

Patch Set 2 does this.

 }
 
 IntSize DeferredImageDecoder::size() const {
@@ -267,7 +266,7 @@ void DeferredImageDecoder::activateLazyDecoding() {
   // future.)
   m_canYUVDecode = RuntimeEnabledFeatures::decodeToYUVEnabled() &&
                    (m_filenameExtension == "jpg");
-  m_hasColorProfile = m_actualDecoder->hasColorProfile();
+  m_hasColorProfile = m_actualDecoder->hasColorSpace();
 
   const bool isSingleFrame =
       m_actualDecoder->repetitionCount() == cAnimationNone ||