People *REALLY* need to get into the habit of tagging their images with an ICC profile describing the color space that it renders into, and paying attention to black point matching.
Just imagine how much confusion you might have if your system
could not handle color tagging at all, or worse, you found that Firefox can handle V2 profiles, but not V4 (Still!??), but the internal PDF display can't handle any (What?!?), while the OS's internal systems handle everything just fine. (Preview, Safari, etc.)
Heck, you might get into the horrible situation of just assuming "everything is an sRGB", or worse, think that everything is 2.2 gamma and hard-code color constants that break on mouseover. (As opposed to 2.4 gamma over most of the color space, and linear in the dark colors, according to the standard, or systems that assume 1.8 gamma for print matching) (sorry, links to those samples lost), or assume that "Hey, my monitor makes 0,0,0 look noticeably different than 1,1,1, so everyone's monitor must behave the same" and make the black-point for a game down at 0,0,0, and assume that if the display is putting out a 3,3,3 grey that it can be told apart from the 0,0,0 black, and that contrast line is visible. (Notch balanced Minecraft's display to look just fine on a low-gamma LCD, but we need a "black level" control to really adjust the darks on well-tuned monitors)
Or worse, a movie playback program that won't let you tell it the color profile of the source movie, that only has TV-like brightness/contrast controls, so it's really hard to adjust the dark areas properly without messing up something in the middle.
... hmm, that last one is all of them, isn't it? Vlc, mplayer, quicktime player -- none of them let you even do a gamma correction, or black-point correction, let alone an actual color-space error.
nice to see this is being added! to vanilla which since i support the stay on 1.7 movement i'll never be able to use, but still pretty nice
