I see the BIG difference in color shift/brightness, etc... when viewing the exact same posted pics on FM with Firefox 3.5 vs. IE 8? Does anyone else see the same thing?
I do not have calibrated monitor and now not sure which browser gives me a more accurate colors.
So just a simple question: Which browser gives you more accurate color? Personally the firefox 3.5 looks better to me. Thanks
Dan

In FF 3.5 color management enabled by default... so it is more accurate i assume

Melnik wrote:
In FF 3.5 color management enabled by default... so it is more accurate i assume

My thought was the same. Thanks.
Dan

'more accurate' color would only mean that images arent properly color encoded (profile) and the browser displays it as a incorrect color correction.

SO i'd say that as long as you embed your profiles or export as srgb only you wont have any color inconsistencies.

Firefox 3.5 has a Javascript vulnerability that could allow a booby-trapped website cause some damage/install rogue software.

To fix it, browse to "about:config" in Firefox, and then pop "jit" into the filter search box. Toggle the "javascript.options.jit.content" to FALSE. This should revert the JS rendering back to 3.0 until a fix is released.

Found this covered in the following Security Fix article:
http://voices.washingtonpost.com/securityfix/2009/07/stopgap_fix_for_critical_firef.html?wprss=securityfix

It seems that a more appropriate forum for this question may have been the Post Processing Forum, but at any rate, if your monitor is not calibrated, there is no way to tell which might be more accurate on your monitor. In this case, two wrongs might make a right.

Barry

The same source now says that the hole has been plugged:

http://voices.washingtonpost.com/securityfix/2009/07/firefox_update_plugs_critical.html


axe9 wrote:
Firefox 3.5 has a Javascript vulnerability that could allow a booby-trapped website cause some damage/install rogue software.

To fix it, browse to "about:config" in Firefox, and then pop "jit" into the filter search box. Toggle the "javascript.options.jit.content" to FALSE. This should revert the JS rendering back to 3.0 until a fix is released.

Found this covered in the following Security Fix article:
http://voices.washingtonpost.com/securityfix/2009/07/stopgap_fix_for_critical_firef.html?wprss=securityfix