That line makes a bit more sense in context:
In iOS 10, the UIColor
class uses the extended sRGB color space and its initializers no longer clamp raw component values to between 0.0
and 1.0
. If your app relies on UIKit to clamp component values (whether you’re creating a color or asking a color for its component values), you need to change your app’s behavior when you link against iOS 10.
"Clamp[ing] raw component values to between 0.0
and 1.0
" means that when you passed the old API a value below 0.0
, it would use 0.0
instead, and when you passed the old API a value above 1.0
it would use 1.0
instead.
UIKit no longer does this. In the new extended-sRGB color space, an RGB triplet like (1.0, 0.0, 0.0)
means "as red as sRGB can get", but it's now also possible to create colors like (1.1, 0.0, 0.0)
that are even redder.
If in iOS 9 or earlier you were passing values outside the 0.0
-1.0
range to UIColor
, it'll now accept those values, so you'll now get different colors than you did before. If you were only ever passing values in that range before, then there's no change for you.
As noted in comments, there's a lot more info in the WWDC16 session on Wide Color.