UX change: have a single SAVE button at the top for BO form pages ?

[matks]

Following #21460 @TristanLDD actually mentioned a new idea.

The idea would be to have, for every pages with forms, a single SAVE button at the top of the page either next to "Recommended modules" and "Help" buttons or replace them (in this case we would need to move these 2 buttons somewhere else).

Not only this single SAVE button would be easy to use, at the top, but also it would be disabled until user modifies something in the form. At this moment it would become enabled and clickable.

This however raises multiple questions:

• Is that suitable for ALL BO pages with a form ? for example inside Taxes BO page there is a listing ; and below the listing is a small form. So when user opens the page he would see only the listing (he needs to scroll to see the form) with a SAVE button: weird
• How does this work if, inside the page, there are 2 forms, very different, which (currently) have each their SAVE button ?
• Technical details: how do we manage and render this button ? Do we hide the current SAVE button but it's still in the DOM, and trigger it using JS when user hits the global sticky-at-the-top SAVE button ?

[prestashop-issue-bot]

Thanks for opening this issue! We will help you to keep its state consistent

[MatShir]

Issue #14018 that might be related to readjustment of the form

[ElodieOS]

Hi everyone! Yes, I think it's a great idea.

Actually, I'm checking all the forms to see if it's possible. If it is, the save button will be at the bottom of the screen, in a sticky position. It will be disabled if there are no changes and enabled if there are one or more changes.

I'll let you know if this issue is possible after my inventory :)

[ElodieOS]

Hi @matks
I checked all the form pages in BO and I don't see any problem to create a unique save button.

So, as I said just before, I think we can put a save button at the bottom of the screen to keep a logical flow (first you can change the settings and then you can save your actions). This button will be in sticky position to allow saving at any time (without scrolling endlessly especially when the form is big).

Two states:

• If you have not made any changes, the save button is disabled.
  

• If you have made one or more changes, the save button becomes active.
  

Special case:

• When you have a data table before a parameter list (like @matks said with the Taxes page for example), we don't need this mechanism because I can't find a data table with multiple parameter lists. Often you only have one parameter to change, so you can keep a "normal" save button (as is the case on the BO currently).
• I can't find a case with two different forms in the same page. Maybe you have an example?

In terms of design :

• Takes the whole width of the screen to make it clear that the save applies to the whole page
• Has the same padding as the header to keep consistency and harmony
• A border of 1 px on the top

Don't hesitate if you need more information :)