After #55092 we have wide gamut support in the iOS engine, and after #127852 we'll have wide gamut support on Android.

Users have asked for ways to represent those colors inside of the framework so they can do things like:

Container(color: Color.displayP3(0.0, 0.0, 1.0, 1.0))

It's important that we don't change the meaning of old colors, that's why a normalized constructor for the Display P3 colorspace would be preferable.

I presume users would want to clip wide gamut colors to sRGB if their app is run on a device/platform without wide gamut support. It's unclear to me if that's acceptable to designers. If someone is making an iOS only app though they can pretty confidently known that wide gamut support will be supported.

This should have almost no effect on engine performance since the capability for wide gamut will already exist by virtue of having support for images.

We have to consider also the ramifications for Web and Desktop platforms. The absence of support for wide gamut colors in those platforms will become more apparent if the framework is updated to support them.