Broswers and CM, FF3 vs. Safari
Broswers and CM, FF3 vs. Safari
- Subject: Broswers and CM, FF3 vs. Safari
- From: Nov06 <email@hidden>
- Date: Wed, 30 Apr 2008 14:49:34 +0200
Hi everybody,
just to gather some opinons. Content displayed by a browser can be put
into roughly three categories,
- CSS (including text)
- images
- plugins (Flash, QT, etc.)
Currently essentially only Safari (both on Windows and Mac) uses CM
for images containing an embedded profile and for those tagged with
sRGB or Adobe RGB (since Leopard, not sure about Windows or the latest
Safari on Tiger). With Firefox 3 coming out of beta soon, it also add
CM for images and also CSS (CM in FF3 is currently disabled by default
however). One reason why it is disabled is the performance hit
(10-15%). For the same reason Safari does not apply CM to CSS content
(as Dave Hyatt blogged about some time ago).
Some points to discuss:
- Is there a way to deal with plugins? Ideally they themselves become
CM aware, QT might do so at some point maybe?
- Can plugin output be hijacked by the browser or the OS to apply CM?
- What color profile to assume/apply to untagged content, ie, CSS
content, untagged images, plugin output? Generic RGB, ie, monitor
profile or sRGB?
- Is the performance hit acceptable?
- Should this [CM for untagged content] be automatic or something
webpages should trigger (well this is rather a kind of global tagging)?
- What to do about some content being CMed (images, CSS) and others
not (CSS, plugins)?
- And finally a more general question, should the whole OS (ie, the
UI) be moved from generic RGB to some color space? It would solve the
issue with the Mac UI being designed for a gamma of 1.8 but often
viewed with a gamma of 2.2?
Looking forward to your opinions.
Markus
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden