Commit 51b5b7bc authored by Miguel Casas-Sanchez's avatar Miguel Casas-Sanchez Committed by Commit Bot

kUseMonitorColorSpace: mark DISABLED_BY_DEFAULT

Mark kUseMonitorColorSpace disabled by default to avoid
the blue-color-looks-purple problems detailed in the bug.
This is just a temporary CL to allow cherry-picking it
into the beta branch.

TBR=dcastagna@chromium.org

Bug: 809909
Change-Id: I35bb8cc48c26091cb1752d3d7709a48d23fb4c6e
Reviewed-on: https://chromium-review.googlesource.com/1012305Reviewed-by: default avatarMiguel Casas <mcasas@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551152}
parent 91193e73
...@@ -68,7 +68,7 @@ const base::Feature kHighDynamicRange{"HighDynamicRange", ...@@ -68,7 +68,7 @@ const base::Feature kHighDynamicRange{"HighDynamicRange",
// Enables using the monitor's provided color space information when rendering. // Enables using the monitor's provided color space information when rendering.
// TODO(mcasas): remove this flag http://crbug.com/771345. // TODO(mcasas): remove this flag http://crbug.com/771345.
const base::Feature kUseMonitorColorSpace{"UseMonitorColorSpace", const base::Feature kUseMonitorColorSpace{"UseMonitorColorSpace",
base::FEATURE_ENABLED_BY_DEFAULT}; base::FEATURE_DISABLED_BY_DEFAULT};
#endif #endif
} // namespace features } // namespace features
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment