Currently UI places submit button at the top of long form interfaces, which creates a suboptimal user experience. When users fill out lengthy forms, they need to scroll back to the top to save their changes. This interrupts the natural workflow and can be confusing for users who expect to find action buttons at the bottom of forms, which is a common UI pattern.
Suggested solutions
The proposed change would either:
Add a second save button at the bottom while keeping the top one (to accommodate different user preferences and avoiding futher confusion)
Move save button to the bottom of the form
Originally created by @em411 on GitHub (Nov 15, 2024).
Original GitHub issue: https://github.com/moghtech/komodo/issues/190
# Description
Currently UI places submit button at the top of long form interfaces, which creates a suboptimal user experience. When users fill out lengthy forms, they need to scroll back to the top to save their changes. This interrupts the natural workflow and can be confusing for users who expect to find action buttons at the bottom of forms, which is a common UI pattern.
# Suggested solutions
The proposed change would either:
1. Add a second ``save`` button at the bottom while keeping the top one (to accommodate different user preferences and avoiding futher confusion)
2. Move ``save`` button to the bottom of the form
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @em411 on GitHub (Nov 15, 2024).
Original GitHub issue: https://github.com/moghtech/komodo/issues/190
Description
Currently UI places submit button at the top of long form interfaces, which creates a suboptimal user experience. When users fill out lengthy forms, they need to scroll back to the top to save their changes. This interrupts the natural workflow and can be confusing for users who expect to find action buttons at the bottom of forms, which is a common UI pattern.
Suggested solutions
The proposed change would either:
savebutton at the bottom while keeping the top one (to accommodate different user preferences and avoiding futher confusion)savebutton to the bottom of the form@mbecker20 commented on GitHub (Nov 16, 2024):
Second save button should work
@gitcatpeter commented on GitHub (Nov 24, 2024):
...or button "jump to the top"