The Javascript API testRunner.setColorProfile is racy (with respect to rendering results) with --enable-color-correct-rendering, and has been disabled.
But, fast/media/mq-color-gamut-api.html depends on this API (in a non-racy way).
We're testing non-sRGB rendering in the virtual/exotic-color-profile tests now, so we can remove the old uses of testRunner.setColorProfile, then un-break the API, and then re-enable this test.
Comment 1 by bugdroid1@chromium.org
, Jun 13 2017