Chromium flag to enable accelerated YUV decoding

content/public/common/content_switches.cc

Index: content/public/common/content_switches.cc
diff --git a/content/public/common/content_switches.cc b/content/public/common/content_switches.cc
index fca420af4d83c3677a58cdcb55fe969545af1f0c..9196386e3652c6a0fb8d2bc4bfe4334f133330bf 100644
--- a/content/public/common/content_switches.cc
+++ b/content/public/common/content_switches.cc
@@ -277,6 +277,12 @@ const char kDisableZeroCopy[]               = "disable-zero-copy";
 // based tests.
 const char kDomAutomationController[]       = "dom-automation";
 
+// Enable partially decoding jpeg images using the GPU.
+// At least YUV decoding will be accelerated when using this flag.
+// Has no effect unless also using --force-gpu-rasterization.

[Stephen White, 2014/09/26 20:41:31]

Technically, this isn't true: you could also get there with the meta
tag + device whitelist.

Maybe "unless GPU rasterization is enabled"?

[sugoi1, 2014/09/29 14:57:27]

Done.

+const char kEnableAcceleratedJpegDecoding[] =
+    "enable-accelerated-jpeg-decoding";
+
 // Enable bleeding-edge code to make Chrome draw content faster. The changes
 // behind this path are very likely to break lots of content.
 // ** DO NOT use this flag unless you know what you are doing. **