Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
With the introduction of wide color support in iOS 10, some color API that were previously accepting a range of 0.0-1.0 for rgba values, are now accepting values in a wider range (negative, >1.0).
We need to check to make sure our API supports the same range as the underlying iOS API.
Yes looks like the doc for UIColor agrees with you: https://developer.apple.com/reference/uikit/uicolor
Quick test in Objective-C shows that negative values are allowed.
@Alex, this should not affect the API signatures but it's worth fixing before the release.
I have reviewed CGColor, NSColor, UIColor, CGColorSpace and a grep of rgb in our manual bindings and could not find a single instance where we are checking values are higher than 1 or lower than 0 (negatives) or usage of any unsigned type.
That answers our (lack of) need to update such code, thanks!