Adds monitor ICC profile support for win and mac

content/renderer/renderer_webkitplatformsupport_impl.cc

Index: content/renderer/renderer_webkitplatformsupport_impl.cc
diff --git a/content/renderer/renderer_webkitplatformsupport_impl.cc b/content/renderer/renderer_webkitplatformsupport_impl.cc
index 32a708655c01c73b0daf9f4ae3a617b0d896f12e..3006cae0419552e29fdd8abbd0b05221c86cc677 100644
--- a/content/renderer/renderer_webkitplatformsupport_impl.cc
+++ b/content/renderer/renderer_webkitplatformsupport_impl.cc
@@ -658,6 +658,19 @@ RendererWebKitPlatformSupportImpl::signedPublicKeyAndChallengeString(
 
 //------------------------------------------------------------------------------
 
+void RendererWebKitPlatformSupportImpl::monitorColorProfile(
+    const WebKit::WebString& type,
+    WebVector<char>* toProfile) {
+  std::vector<char> profile;
+  gfx::NativeViewId view_id = 0;
+  std::string type_str(type.utf8());
+  RenderThreadImpl::current()->Send(new ViewHostMsg_GetMonitorColorProfile(
+      view_id, type_str, &profile));
+  *toProfile = profile;

[abarth-chromium, 2012/06/19 20:36:50]

Is this information cached in WebCore?  I seem to remember that we only read
this information when we start up the image decoders.

When you land this patch, you should watch the perf bots to see if this causes a
startup time regression.

[tpayne, 2012/06/19 21:44:52]

Yes, it is cached in WebCore. We only read it the first time we decode an image
with an embedded ICC profile.

+}
+
+//------------------------------------------------------------------------------
+
 WebBlobRegistry* RendererWebKitPlatformSupportImpl::blobRegistry() {
   // ChildThread::current can be NULL when running some tests.
   if (!blob_registry_.get() && ChildThread::current()) {