Firefox uses qcms, a modified lcms version which aims performance over quality and (unfortunately also) compatibility (q = quick). I wonder why Firefox doesn't bring back lcms now that PCs got faster in the last years and Firefox started to use a lot of reasources anyway. For example: qcms doesn't support lookup table based profiles (compatibility problem) and prefers speed over quality (which sounds stupid since color management should be all about quality, not speed - even if some optimizations are necessary in some cases, but optimizations, not speed over anything else thinking...). 2012/4/21 George Pop <gapop@xxxxxxxxxxx>: > Hi, > > Can you please say more about this? In what respects is Firefox's CM broken? > In my informal tests, and judging results on a monitor that only covers the > gamut of sRGB, Firefox seems to perform the same as any color-managed > application. It does the right thing for images that are tagged with a > different color space than sRGB, unlike Chrome. > > George > > >> Date: Thu, 19 Apr 2012 18:31:16 +1000 >> From: graeme@xxxxxxxxxxxxx >> To: argyllcms@xxxxxxxxxxxxx >> Subject: [argyllcms] Re: Color management in google chrome > >> >> Becker Béla wrote: >> > On windows you can choose between Safari and Firefox if you need colour >> > management. >> >> Firefox uses a rather broken CMM library though. >> >> Graeme Gill. >>