You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been wondering about the 2 popular styles seen in forms which are inline controls and options in the keyboard area.
The nice thing about the keyboard area is, that many implementations provide "next" and "previous" buttons to easily step through the form.
On the other hand there are incredibly simple forms with editing capabilities where the user can easily select the next field at the bottom of the screen.
We should probably decide on a common way for the default controls.
Looking forward to your input.
The text was updated successfully, but these errors were encountered:
By "row editors" do you mean row navigation or something else? I had started a branch 031e208 for navigation that will need to be heavily reworked.
If you could attach some screenshots of the options you mean, that would be helpful 📷
fcanas
changed the title
Global "option" for row editors as inline relement or keyboard-like inputs
Global "option" for row editors as inline element or keyboard-like inputs
Aug 18, 2015
I have been wondering about the 2 popular styles seen in forms which are inline controls and options in the keyboard area.
The nice thing about the keyboard area is, that many implementations provide "next" and "previous" buttons to easily step through the form.
On the other hand there are incredibly simple forms with editing capabilities where the user can easily select the next field at the bottom of the screen.
We should probably decide on a common way for the default controls.
Looking forward to your input.
The text was updated successfully, but these errors were encountered: