19 comments

  • Stuart McCoyStuart McCoy, 8 years ago (edited 8 years ago )

    It has to do with the way the image was saved. Photoshop allows you to add a color profile to the image and Safari is able to read this while most other browsers (STILL?!?!?) don't seem to be able to. Chris Coyier has a write-up about this (http://css-tricks.com/color-rendering-difference-firefox-vs-safari/) on CSS Tricks from 2008!!!

    22 points
    • Ivan VásquezIvan Vásquez, 8 years ago

      So I take it we should always save images with the sRGB color profile to ensure colors are rendered properly?

      2 points
  • Robbert EsserRobbert Esser, 8 years ago

    Internet Explorer agrees with Safari and IE is always right

    13 points
  • Zsolt IZsolt I, 8 years ago

    Safari is doing it right, chrome is doing it wrong. If you save the image from each browser the save version looks like Safari (at least on a Mac).

    Therefore the correct version is Safari.

    7 points
    • Phil RauPhil Rau, 8 years ago

      Yeah, but it makes sense that Preview would use the same color handling as Safari... what about Photoshop?

      3 points
      • Ruben HRuben H, 8 years ago

        Exactly. I know that preview isn't able to handle CMYK well. Photoshop does.

        0 points
  • Ryan LeFevreRyan LeFevre, 8 years ago (edited 8 years ago )

    Technically Safari because it actually reads embedded color profiles, while other browsers don't bother.

    6 points
  • Andrew Parker, 8 years ago

    As I understand it - this is all down to the way different browsers handle color management, and what they do with images that are untagged:

    http://cameratico.com/guides/web-browser-color-management-guide/

    Personally I also see horrible color management shifts when I connect my external monitor and the browser window moves into the new space. Seems like this is all a bit of a mess?

    6 points
  • George PapadakisGeorge Papadakis, 8 years ago

    Firefox agrees with Chrome and thus Chrome's take has to be the winning one.

    5 points
  • Cihad TurhanCihad Turhan, 8 years ago

    IE agrees with Safari, Firefox agrees with Chrome.

    Brace yourself, the war is coming :)

    2 points
  • Ismet TrakoIsmet Trako, 8 years ago

    Safari.

    2 points
  • Giulio MichelonGiulio Michelon, 8 years ago

    Safari colors are always different. Don't know why.

    2 points
  • Gabriel BrodersenGabriel Brodersen, 8 years ago (edited 8 years ago )

    Having read the other comments, I might sound like a complete newbie here, but boy do I hate color profiles with a passion! And boy do I feel they cause a lot of problems and confusion for many people, just as many are having difficult explaining how to work with them.

    Considering how rarely anyone should have to bother with color profiles – even have to hear the term used – it still surprises me how much trouble these things cause for simple user, who maybe just want a color in a file to match elsewhere, like in a presentation or on a website.

    In my mind, color profiles should be a term hidden away, deep in the system, where only skilled professionals will have to bother with it, if they can find it.

    Can anyone explain to me, why there should ever be a difference between the same color code in different web browsers, graphic applications, or whatever isn't printed or used outside the screen (unless intensionally decided by the user)?

    Is it wrong of to suspect that Chrome & Firefox intended not to let their browsers be affected by color profiles, in order to maintain color consistency (ironically the same color profiles try to achieve)?

    1 point
  • Daniel ArcherDaniel Archer, 8 years ago

    I always vote for Safari.

    Can we take a quick poll? Which web developers here use Safari or Chrome?

    0 points
  • elkraneo …elkraneo …, 8 years ago

    http://css-tricks.com/color-rendering-difference-firefox-vs-safari/

    0 points
  • Surjith S MSurjith S M, 8 years ago

    Adjust your brightness!!!

    0 points