D8UX: Improve the position of the 'Save' button on Modules page.

We should be very carefull with placing a (submit) button in different places. During the training I see the confusion when users are confronted with inconsistent patterns. After one day training with only Drupal core, they start using Views on the second day. There they look for the submit button on the bottom of the screen but can't find it.

With the case of node edit forms, the solution of using vtabs that we came up with didn't require moving the buttons around. This is different though in that now the node edit forms don't require much scrolling around from the users.

I understand that users expect submit buttons to be at the bottom of any form they use and that this is something they are accustomed to, but the two examples used here (the Modules page and the Views edit page) have something in common between them that sets them apart from normal forms: they are both -unavoidably- a huge labyrinth of widgets and controls. People using these pages are already struggling in order (learn how) to accomplish the task(s) they serve and my personal opinion is that their top priority is usability rather than consistency with the rest of the site's placement of submit buttons.

In other words, if placing the buttons elsewhere proves to help their tedious admin tasks, users simply won't mind - trust me ;)

@kIonos: I was only talking about the modules page. Please let's keep this issue focused on that.

I can see that there would be problems with breaking with the established user expectations on this form. Is there consensus on the problem I listed above?

I would be with any kind of solution that alleviates the frustration caused with having to scroll down the ENTIRE module page just because I checked something near the top to enable. Seriously, why has this never come up before? It's a major pain.

List of possible solutions:

• an active notification is present whenever a change to a module is made. That notification would contain text informing the user of their selected action(s) and provide a save button.
• a keyboard shortcut (like Ctrl+Enter) is hooked into the form save action and notification is present whenever a change happens informing the site admin that if they press Ctrl+Enter the set of changes will happen.
• a save button appears on the side and intelligently remains on the screen as the user scrolls down the page. The final save button survives.
• we completly change how all forms are rendered to impose the new paradigm espoused here

Can anyone think of alternative solutions?

Hm. I don't really support this on a one-off basis, because of the user behaviour I've observed and Sutharsan confirms: consistent UI patterns are really useful and it's very jarring when things don't conform to them.

I actually don't run into this issue, myself. I know that I can hit "cmd+down arrow" and be at the submit button of any form in all of Drupal (except apparently Views in D7, which is a bug, not a feature IMO). I would not like it if one particular long page had a "floaty" submit button, but no other long pages in Drupal (e.g. node form with > 30 fields, permission page, etc.) did. Consistency++;

I recognize that the position of the save button can be a problem, but in this case is caused by the length of the page. Not by the position itself. So lets solve the cause, and not fight the symptoms. If we can't reduce the size, we can still try to mitigate the problem with a different position of the save button. So, until then I'll go back to #538904: D8UX: Redesign Modules Page.

IMO this is a "won't fix". I prefer having a consistent UI over a custom fix.
Just installthe Form Save module, and you can save any page with [CTRL+S]

If making it sticky is out of the question, then could we think about adding it somewhere in the toolbar?

Fixing tag.