My old thread regarding the problem in 27.4.2: viewtopic.php?f=37&t=16546
and before that here: http://www.murga-linux.com/puppy/viewtopic.php?t=111420 ( with example pics)
I set the gfx.color_management.mode to 0 in 28.7.2, and the problem disappeared (again).On gfx.color_management.mode, kb.mozillazine.org wrote: Possible values and their effects
0) Disable color management.
1) Enable color management for rendered graphics.
2) Enable color management for tagged graphics only. (Default)
Note: These values apply to Firefox 3.5 and SeaMonkey 2. In previous versions, color management was disabled by default via the boolean preference gfx.color_management.enabled set to "false".
Without a properly calibrated monitor and a correct color profile, color management may actually make colors look worse.
Is this a setting that should be default set to 0? I see that there is a reference to a setting in old Firefox and Seamonkey in the quote from mozillazine above, gfx.color_managment.enabled. In PM 28.7.1, there is a setting gfx.color_management.enablev4, is that a recent addition? Apart from those I may see right away, are there any implications if it is set to false?