Open Bug 880271 Opened 7 years ago Updated 5 months ago
Inconsistent color management
User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:21.0) Gecko/20100101 Firefox/21.0 (Beta/Release) Build ID: 20130511120803 Steps to reproduce: I created a handful of elements and made them red (#ff0000) in various ways, using: * CSS * background-color: #f00 * background: linear-gradient(#f00, hsla(0, 100%, 50%, 1)) * background: radial-gradient(#f00, hsl(0, 100%, 50%)) * background: url(no-profile.png) // image with no colour profile * background: url(embedded-profile.jpg) // image with with colour profile * Canvas * c.fillStyle = '#f00'; c.fillRect(0, 0, 200, 200); * SVG * fill: rgb(255, 0, 0) * Image * <img src="no-profile.png"> // image with no colour profile * <img src="embedded-profile.jpg"> // image with with colour profile I have set gfx.color_management.mode to 1 (full colour management) and have a properly calibrated wide gamut monitor. Here is a test page that demonstrates this: https://dl.dropboxusercontent.com/u/41899939/colour-management.html Actual results: The boxes with with colour set by linear-gradient, radial-gradient and a canvas displayed with a very vivid red (i.e., without colour management). The rest were showing the correct red. Here's a screenshot, with an embedded profile (the differences may not be visible on your screen): https://dl.dropboxusercontent.com/u/41899939/screenshot-embedded-profile.jpg Here's another screenshot, as sRGB with no embedded profile (the colours aren't right, but on my screen, imagine the orange squares are red, and the red ones are a very vivid red): https://dl.dropboxusercontent.com/u/41899939/screenshot-srgb.jpg Expected results: All of the boxes should appear to be the same colour.
Component: Untriaged → GFX: Color Management
Product: Firefox → Core
Border colors are not managed too. Test page: https://dl.dropboxusercontent.com/u/8716756/colors.html Screenshot: https://dl.dropboxusercontent.com/u/8716756/colors.jpg
This is still actual in Firefox 26.
This is still actual in Firefox 60.0.2.
You need to log in before you can comment on or make changes to this bug.