Available in the 2018 R2 SP release.

On UWP, the IntegerEditor has a default max value of 100. This is not present on other platforms.

Current Workaround

The workaround is to explicitly set the max value via a NumericalRangeValidator

E.G.

[NumericalRangeValidator(int.MinValue, int.MaxValue)]
public int PropertyName { get; set; }

When DisplayValueFormat is set to an Integer property, Zero value is not applied.

Setting DataFormPasswordEditor inside a custom renderer on Android leads to the following exception:

Java.Lang.NullPointerException: Attempt to invoke virtual method 'java.util.Iterator java.util.ArrayList.iterator()' on a null object reference

If the following data annotations are defined:

[DisplayValueFormat(Date = "MM-dd-yyyy HH:MM tt")]
[ReadOnly]

DisplayValueFormat is not applied properly.

This prevents content below the control to be visible.

Available in the R2 2018 release.

Please refer to the attached project that reproduces the issue. In the MainPage constructor, you can switch between using the PickerEditor (validation works) and the SegmentedEditor (validation doesn't work).

The segmented editor does not change the underlying property immediately.

If an editor does not have positive/negative feedback, an empty text view still appears after validation and shifts the editors.

Available in the 2017 R2 SP release.

There is an empty group title view above the editors even if there are no groups.
The red area on the attached screenshot.

Add FontFamily option to DataFormEditorStyle and DataFormGroupHeaderStyle.

Add TextAttributes option to DataFormEditorStyle and DataFormGroupHeaderStyle (e.g. Bold).

Allow multiple selection from the AutoCompleteEditor using Tokens and properly commit it.

We need to simplify the way the editors can be customized.  XAML only solution would be great.