For the purposes of the "system color space," use the main display's color space

For the purposes of the "system color space," use the main display's color
space instead of a color space derived from the apparently unreliable
system ColorSync profile setting.

BUG=21658
TEST=Rendering works on Nico's girlfriend's laptop

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=26090

[Nico, 2009-09-13 08:15:38]

LG

Ran my local build without and with this patch. Without the patch, the renderer
dchecks in bitmap_platform_device_mac.cc:135, with this patch everything seems
to work fine. I also checked that chromium and safari render the same colors.

[Mark Mentovai, 2009-09-13 15:09:36]

Thanks for the review.  I tried this out myself on a few machines and the colors
are still right.  They match Safari and our post-r25380 behavior.  Getting the
main display's color space from the Quartz Display Manager should be more
reliable than getting the system profile from ColorSync, and the fallback to
generic RGB should at least keep things working in breakdown cases.

Like bug 21114, I'm checking this in now because the bug is pretty bad, it's
apparently affecting a bunch of people, and I want to make sure that the fix
makes 208.  I'd still like to validate the behavior on a display-less system
(accessed, say, via Screen Sharing), but that's not urgent and given the
fallback it can wait until after 208 branches.

[Amanda Walker, 2009-09-13 18:53:46]

LGTM!