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.
Run the code below on an Android device. Move the circular bit on the Slider. The circular bit and the bar that it should move along are drawn separately, rather than the circular bit moving along the bar. My guess is that they have different default vertical options, so the default behaviour is odd. To demonstrate this, first run the code below, then run it again after adding "VerticalOptions = LayoutOptions.CenterAndExpand," to the Slider initialisation.
public class App : Application
MainPage = new ContentPage
Content = new Slider
BackgroundColor = Color.Blue,
Maximum = 255,
Minimum = 0
protected override void OnStart()
// Handle when your app starts
protected override void OnSleep()
// Handle when your app sleeps
protected override void OnResume()
// Handle when your app resumes
*** Bug 28029 has been marked as a duplicate of this bug. ***
Should be fixed in 1.4.3 final.
I have checked this issue with Xamarin.Forms 188.8.131.5264-pre3 and its working
fine on device(NEXUS 5) But I am getting issue on XAP.
Note: On iOS its working fine with both device and simulator.
So as of now I am reopening this issue in respect of emulator.
Microsoft Visual Studio Professional 2013
Version 12.0.30723.00 Update 3
Microsoft .NET Framework
We're going to keep this closed until we see this happen on device. Either way this is a pretty edge case, nobody should really ever be doing this.
Thanks @Jason for clarification.
As per comment #4 closing this issue.