Replies: 2 comments
-
I have just recently come across this exact issue. |
Beta Was this translation helpful? Give feedback.
0 replies
-
great demo any interest in making a PR for these? I would have to stop using date-time to avoid it Cheers |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Based on my own experience I've created together with @grundid a demo app, to showcase the differences between a modified FormBuilder version that implements consistent behaviour for focus and keyboard input and the regular FormBuilder behaviour.
In this demo app we have created two tabs with identical FormBuilder widget configurations. However on the left tab we used FormBuilder widgets that include our focus and keyboard input modifications. You can switch any time between those two forms and compare the focus and keyboard input behaviour. Below the form you can request focus for any of the form elements via a button.
Please have a look at the source code at my prebuild demo-app: https://khirsig.github.io/form_builder_demo/
Source Code for the demo: https://github.com/khirsig/form_builder_demo
The intention of this demo is to be able to focus every input component, and this means that the InputDecorator recieves the focus for the component. At the same time you can switch between mouse/touch input and keyboard input at any time.
What do you think about this idea and would you accept pull requests concerning this topic?
Beta Was this translation helpful? Give feedback.
All reactions