Open Bug 1274036 Opened 8 years ago Updated 1 year ago

Off Main Thread Compositing does not respect OS X display profiles


(Core :: Graphics: Color Management, defect, P3)

46 Branch





(Reporter: brandon.cheng, Unassigned)



(Keywords: regression, Whiteboard: [gfx-noted])

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160502172042

Steps to reproduce:

1. Under OS X Settings -> Displays -> Color, change your display profile to one with a color space other than sRGB. Preferable something that is very different than sRGB on your display. "ACES CG Linear" worked well on my MacBook 12" Retina since its difference between sRGB is very noticeable.
2. Observe browser chrome and website remain rendered in the sRGB color space. Observe context menus change to the new display profile color space.
3. Toggle "layers.offmainthreadcomposition.enabled" to "false" in about:config.
4. Restart Firefox and notice the display profile applied to every element of the browser.

Actual results:

Graphical elements composited off the main thread continue to be rendered in sRGB.

Expected results:

All elements rendered in the browser should be rendered using the system display profile color space regardless of where it is composited.
Here's more information I was able to dig up using mozregression.

1. Before bug 1187322 was fixed, turning off hardware acceleration under Firefox advanced preferences corrected the color behavior. (All parts of the chrome and rendered website rendered in the system color space.)
2. After bug 1187322 was fixed (patch applied in Firefox 45.0), turning off hardware acceleration had no effect. Toggling layers.offmainthreadcomposition.enabled was required instead to show the correct color space.

I have not tested this with other OS X machines yet.
Component: Untriaged → GFX: Color Management
Product: Firefox → Core
Blocks: 1084598
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86_64
Priority: -- → P3
Blocks: 1287763
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.