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.
When using the Stepper on a Danish region Phone, i am unable to use comma in my entry fields.
I want to enter "1,8" but it is converted to "18".
I believe the root cause, is the way Stepper converts to Double
Taken from the source at GitHub:
coerceValue: (bindable, value) =>
var stepper = (Stepper)bindable;
stepper.Value = stepper.Value.Clamp(stepper.Minimum, (double)value);
I Believe the Conversion should be CultureAware, like the Convert.ToDouble() method:
Convert.ToDouble Method (String, IFormatProvider)
More testing done on my part.
My Bug report is wrong, The code i mention is not the culprit.
The Issue remains thou.
Somewhere in Xamarin Binding, there is a Culture-unaware parsing of doubles, that causes Comma to be removed.
Two test cases i made:
string input = "1,9";
double output = double.Parse(input);
string input = "1,9";
double output = double.Parse(input, new CultureInfo("da-DK"));
This appears to be expected behavior per bug 36417.
Since this would be a feature change in Forms, it would be best suited as a proposal in our Evolution forum for future consideration. When submitting a proposal on the Evolution forum, be sure to first read the contribution guidelines so your proposal is ready for discussion with the Forms team and community. Thanks!
*** This bug has been marked as a duplicate of bug 36417 ***