Gamma-correctness pushed into Skia, top-down.

include/core/SkSurfaceProps.h

Index: include/core/SkSurfaceProps.h
diff --git a/include/core/SkSurfaceProps.h b/include/core/SkSurfaceProps.h
index 735561f1dc9180a1cb9f044fa23856ae915f08c1..b165afd8a9487f677676d4ec321212d498ffdc17 100644
--- a/include/core/SkSurfaceProps.h
+++ b/include/core/SkSurfaceProps.h
@@ -54,6 +54,7 @@ public:
         kDisallowAntiAlias_Flag         = 1 << 0,
         kDisallowDither_Flag            = 1 << 1,
         kUseDeviceIndependentFonts_Flag = 1 << 2,
+        kAllowSRGBInputs_Flag           = 1 << 3,

[reed1, 2016/04/04 21:12:29]

Lets add some dox for this...

Among other things, will it apply just to images, or to colors/shaders as well?

[Brian Osman, 2016/04/04 21:42:35]

I would assume it applies to everything, although that could be open to
discussion. It depends on how we plan to handle those kinds of inputs. If we
require people to explicitly give us sRGB (or other non-linear) colors, then
people can't accidentally break legacy mode with those APIs. With images, it's
very easy, because the codecs need to tag most images sRGB. Of course, for
testing purposes, it's probably best to make the flag as global as possible, so
it basically short-circuits the sRGB interpretation of everything?

     };
     /** Deprecated alias used by Chromium. Will be removed. */
     static const Flags kUseDistanceFieldFonts_Flag = kUseDeviceIndependentFonts_Flag;
@@ -75,6 +76,7 @@ public:
     bool isUseDeviceIndependentFonts() const {
         return SkToBool(fFlags & kUseDeviceIndependentFonts_Flag);
     }
+    bool allowSRGBInputs() const { return SkToBool(fFlags & kAllowSRGBInputs_Flag); }
 
 private:
     SkSurfaceProps();