color: Tests for fix accidental partial color conversion

ui/gfx/icc_profile.cc

Index: ui/gfx/icc_profile.cc
diff --git a/ui/gfx/icc_profile.cc b/ui/gfx/icc_profile.cc
index 9f04bd8d77023d5a47274fc1fd4d5487195d7048..9390da64011b8e19a3d985888b9b0b9864d8e258 100644
--- a/ui/gfx/icc_profile.cc
+++ b/ui/gfx/icc_profile.cc
@@ -18,6 +18,7 @@ const uint64_t ICCProfile::test_id_adobe_rgb_ = 1;
 const uint64_t ICCProfile::test_id_color_spin_ = 2;
 const uint64_t ICCProfile::test_id_generic_rgb_ = 3;
 const uint64_t ICCProfile::test_id_srgb_ = 4;
+const uint64_t ICCProfile::test_id_no_analytic_tr_fn_ = 5;
 
 namespace {
 const size_t kMinProfileLength = 128;
@@ -33,7 +34,7 @@ struct Cache {
   ~Cache() {}
 
   // Start from-ICC-data IDs at the end of the hard-coded test id list above.
-  uint64_t next_unused_id = 5;
+  uint64_t next_unused_id = 10;

[msarett1, 2017/02/22 20:58:46]

I don't really understand what's going on here.

[ccameron, 2017/02/22 21:03:27]

This is sort of weird. It's ensuring that we don't use any IDs less than 10,
because they'll conflict with the hard-coded IDs.

It's to paper over the fact that, in Chrome, the IDs are always created in the
browser process, and so are always unique, but during layout tests, some of the
IDs are created in the renderer process (for testing), and we need to make sure
that they don't conflict with the IDs coming from the browser process.

   base::MRUCache<uint64_t, ICCProfile> id_to_icc_profile_mru;
   base::Lock lock;
 };