Bug 19233 - Workaround Apple UISlider thumb tint color bug
Summary: Workaround Apple UISlider thumb tint color bug
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS Designer ()
Version: unspecified
Hardware: PC Mac OS
: Low enhancement
Target Milestone: master
Assignee: Jérémie Laval
Depends on:
Reported: 2014-04-22 22:37 UTC by Amy Burns
Modified: 2014-11-13 05:33 UTC (History)
5 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Amy Burns 2014-04-22 22:37:36 UTC
Slider renders on design surface with thumb at a value of 0.5, however Widget > Slider > Current is set as 0.

See screenshot below:

This is on latest alpha - 4.3.4
Comment 1 Amy Burns 2014-04-23 10:31:02 UTC
On a similar note:
When adjusting the thumb/min/max tintcolors in code behind
  a) max and thumb tintcolor does not render properly
b) when running the application the thumb tint stays at the default color -
(This seems kind of buggy in xcode too though?)

Video showing this

Comment 2 Jérémie Laval 2014-04-23 16:13:54 UTC
Fixed the thumb value issue.

For the slider tint, looks like it's a bug in iOS 7. A quick Google search showed that and a workaround for it.
Comment 4 Jérémie Laval 2014-05-01 11:38:37 UTC
The screencast is referring to comment 2, is that what you intended?

If yes, we are not going to work around that Apple bug for 5.0
Comment 6 Jérémie Laval 2014-05-01 12:10:41 UTC
Yes this is an Apple specific iOS bug. Since we don't want to confuse the user as to why they don't get the result they see on the surface we are not going to workaround it in the designer for now.

The documentation team is aware of the issue and will document it hence marking the bug as low enhancement and tracking for the future.
Comment 7 Alan McGovern 2014-11-13 05:33:05 UTC
Since this is an apple bug, i'm just going to close it. Our side of the issue was fixed already.