The expected behavior when updating the text on a button click, for example,  is to expand the editor.

Currently the editor is expanded when the user starts typing inside it.

 Nullable int property is validated against range when no data is input.

This prevents content below the control to be visible.

Available in the R2 2018 release.

Available in the R2 2018 release.

The Source property should support two way binding.

Available in the R2 2018 release.

With the current implementation in Xamarin.Forms, the control has no built-in support for enumerable properties. The approach is to create custom renderers and use the native editors.  We need to expose default editors for enumerable and custom types.

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

Implement support for changing the template of the group headers.

Add an editor that loads an external view / page to edit a property value.

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

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; }

Provide capability to replace the native view with Xamarin Template.

Built the SDKBrowser project for iOS, using VS 2017 and latest stable Xamarin.Forms.
When editing a field, the OS keyboard appears and above it are "Prev" and "Next" buttons for moving between form fields.  Those buttons behave erratically.  Attached 2 images.

01: the 1st field is focused.
02: after pressing Next, the 3rd field is focused ("Age").

Pressing Next again does not change which field is focused, and Prev becomes active.  Pushing either Prev or Next does nothing at all.

Available in minor release 2018.1.202. It will also be available in the R1 2018 SP release.