Introduce autosaving for changes made on user settings page

Problem to solve

The user needs to confirm the changes made on the settings page by clicking on the 'Save changes' button. The problem is that the button is way below the fold so the user needs to scroll to find it. Only then can they save their changes.

Further details

We've been thinking about best approaches to introduce autosaving to settings pages via gitlab-design#121 (closed). There's a draft for the guidelines and they should be completed by the end of 11.5. Then we need a 'pilot' where we first introduce autosaving changes to see how it works in practice and work out small details.

Proposal

Auto-saving changes and informing the user that the changes were saved via toast messages:

image

And on mobile:

What does success look like, and how can we measure that?

User settings page without the need to manually confirm changes.

Links / references

cc @akaemmerle @jeremy_

Edited Oct 25, 2018 by Matej Latin
Assignee Loading
Time tracking Loading