Adrian Stabiszewski

A possible solution or workaround to this is to create your own ValueAccessor. The example below is for a DateTimePicker, but you can easily adapt it to DatePicker only. Don't...

Thank you for looking into it and sorry for missing the stack trace. I reverted my system back to angular 5.2 and dart 2.2.0 where this problem does not occur....

No, not yet. I don't have a link.

How do we proceed here? If you look at the latest PR #1062 people are trying to solve the strange behavior of requestFocus/ensureVisible and adding new flags (autoScrollToInvalidField) to compensate...

@ashim-k-saha Thanks for looking into it. Disposing of the focusNode from the widget is one problem, but this is not the issue here. The focusNode that is created in the...

Yes, this is still a problem. As described above the attach method has to be called. At some point the "shouldRequestFocus" option was added to the form elements, basically to...

Sure, will do that. Could we please find a better solution and get rid of the "shouldRequestFocus" option? If the focus is working OK the option is not really needed....

Oh yeah, issue #880. I fixed this issue like this in my fork because users stared complaining about the list jumping back and forth ;) ```dart void requestFocus() { FocusScope.of(context).requestFocus(effectiveFocusNode);...

Please join our discussion about keyboard navigation in forms at https://github.com/flutter-form-builder-ecosystem/flutter_form_builder/discussions/1297 Have a look at our demo app linked in the discussion. It showcases exactly your desired behavior.

Hi im working with @khirsig on improving this library and the user experience. After looking at the native Flutter form components we can only see two form fields that extend...