-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
flutter/engine
#34464Closed
Copy link
Labels
a: desktopRunning on desktopRunning on desktopengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.found in release: 3.0Found to occur in 3.0Found to occur in 3.0found in release: 3.1Found to occur in 3.1Found to occur in 3.1frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer version
Description
It looks like the image's color profile is ignored and colours are assumed to be in the target color space, which appears to be sRGB on iOS and Display P3 on macOS. Similarly, painting done by Flutter also occur in sRGB for iOS and Display P3 for macOS.
These two images of both filled with RGB(255, 0, 0) but on having the sRGB color profile and the other Display P3 (the color in the image on the right should look more intense on monitors supporting Display P3):
| sRGB | Display P3 |
|---|---|
![]() |
![]() |
| iOS | macOS |
|---|---|
![]() |
![]() |
Originally posted by @spkersten in #96733 (comment)
ViliusP
Metadata
Metadata
Assignees
Labels
a: desktopRunning on desktopRunning on desktopengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.found in release: 3.0Found to occur in 3.0Found to occur in 3.0found in release: 3.1Found to occur in 3.1Found to occur in 3.1frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer version



