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 for Bug 41960 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
If a stepper has both the Value and Maximum properties data-bound and the initially bound Value is greater than 100, the stepper automatically changes the Value to 100.
I believe this is caused because Maximum property is most likely defaulted to 100 and the Value property is probably bound before the Maximum property. When the Value is bound, it probably uses the current Maximum of 100 to validate / update the Value.
I worked around the issue by using the following logic:
// Initialize elements so we can reference the stepper by name.
var viewModel = new MyViewModel();
// Manually bind Maximum
MyStepper.Maximum = viewModel.Maximum;
// Allow Xamarin to data-bind as usual
BindingContext = viewModel;
Created attachment 17008 [details]
You don't need to create a workaround like above. Simply swap the order value and max are data-bound. You already wrote a similar comment:
// Note that if you swap the order of these two lines, the stepper will have the correct initial value
I'd be interested to know how this issue could be solved. In my opinion, this should not be treated as a bug.
Putting back to confirmed for Stephane to take a look at this. The offered PR doesn't satisfy the issue.