On Jan 20, 2008, at 11:03 AM, Henri Sivonen wrote:
On Jan 20, 2008, at 19:58, Darin Adler wrote:
But this rule not yet implemented in WebKit. Instead, when
displaying on screen, today's WebKit treats untagged color as if it
was in the system's primary display device's color space. This
means that no color correction is applied to such colors.
Yes, and the sRGB approach would Break the Web as long as the Flash
plug-in doesn't participate.
That's one reason we don't correct untagged colors yet, but this is a
solvable problem.
or whether the Mac OS X gamma difference from Windows is important
when designing this.
The gamma difference is the foremost problem being "solved" but it
would be by far easier to solve by changing the Mac OS X default
gamma to match Windows. Computing color space transformation just
because Mac OS X is stuck with an unusual default gamma value is an
overkill. Sure, there are other color space differences, but most of
the time for most people, the non-gamma differences are less
important.
I think the sRGB design is a good one.
I disagree. Why would you want a brand new Cinema display emulate
the gamut of an office CRT from the previous millennium potentially
by clipping instead of stretching the colors to gamut of the device
at hand?
Wouldn't changing the default gamma have essentially the same effect
(with the added difference that even profile-tagged images could not
take advantage of wider gamut)?
Cheers,
Maciej
