When using an SfDataForm in a Xamarin.Forms UWP program, DataObject properties decorated with [DataType(DataType.Password)] are not set correctly -- they are set to all dots instead of the value that was typed into the field. This works correctly in the Android and iOS versions of the program.
This is using the latest release version of all applicable NuGet packages.
JNJayaleshwari N Syncfusion Team January 25, 2019 11:03 AM UTC
Thanks for contacting Syncfusion Support.
We have checked the reported query related to setting DataType.Password in SfDataForm Xamarin Forms UWP platform in our latest version. But unfortunately the reported issue does not reproduce at our end. We have created a sample with data form item using Password as DataType which renders as password type in UI as expected.
We have attached the tested sample for your reference and you can download the same from the following location.
Could you please check with the provided sample and revert us whether the issue is reproduced? Else, kindly modify the provided sample with replication procedure along with more details regarding your query with screenshots if possible. So that it will be helpful for us to analyze and provide you possible solution.
CMChris MarinacciJanuary 25, 2019 05:53 PM UTC
It looks like it is validation that messes up the value. To reproduce the bug using your sample:
3. Set a breakpoint on the line after the one that begins with "String password".
4. Run the UWP version of the program and click the "Validate" button.
When the breakpoint is hit, you will see that the value of "password" is all dots instead of the actual password value.
JNJayaleshwari N Syncfusion Team January 29, 2019 11:14 AM UTC
We have validated the defect you have initiated with us. Thank you for taking the time to report this issue with “Actual password value is not committed in data object while using password editor in Xamarin Forms UWP” and helping us improve our product. At Syncfusion, we are committed to fixing all validated defects (subject to technological feasibility and Product Development Life Cycle ) and including the defect fix in our subsequent Volume 1, 2019 release, which is expected to be available by middle of the month March, 2019. If you wish to receive this fix in a specific prior release product version please contact Syncfusion Support (backwards compatibility subject to technological feasibility and our Support SLA) You can now track the current status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link.