Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Not visible "Save" button in Settings #5978

Closed
rivadav opened this issue Aug 11, 2014 · 8 comments
Closed

Not visible "Save" button in Settings #5978

rivadav opened this issue Aug 11, 2014 · 8 comments
Labels
answered For when a question was asked and we referred to forum or answered it. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Milestone
Backlog (Help wan...

Comments

@rivadav
Copy link

rivadav commented Aug 11, 2014

Settings

Problem
Since most of the settings need additional confirmation after editing them, this action should be easily accessible to users. Currently, "Save" button is in different places and sometimes users have to scroll in order to see it.

Sometimes it's also not clear if "Save" relates only to specific section or the whole page (like in Trusted Piwik Hostname).

wlnpyhzku5

Proposed solution
One of possible solutions is to place "Save" button on the bar which will be pinned to the bottom of screen. Thanks to this, it will be always easily accessible and there'll be confusion to which section it relates to.
However, it must used cautiously with in-line edition of elements to avoid confusion.

screenshot-2014-08-11-15 51 42_proposed
@mattab mattab added this to the Short term milestone Aug 11, 2014
@mattab
Copy link
Member

mattab commented Aug 11, 2014

Thanks for the suggestion!

@mattab mattab added c: Usability For issues that let users achieve a defined goal more effectively or efficiently. and removed c: UI - UX (AngularJS twig less) labels Oct 12, 2014
@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Dec 1, 2014
@mattab mattab mentioned this issue Dec 1, 2014
Closed
@mattab mattab mentioned this issue Apr 7, 2015
Closed
@mattab mattab removed the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Apr 9, 2015
@mattab
Copy link
Member

mattab commented Sep 22, 2015

Maybe this is easy to add? it's a small trick, but would really help first-time users!

@mattab mattab modified the milestones: 2.15.0, Short term Sep 22, 2015
@tsteur
Copy link
Member

tsteur commented Oct 2, 2015

Proposed solution sounds a bit like a floating action button ( https://www.google.de/design/spec/components/buttons-floating-action-button.html ) which also has some downsides ( see eg https://medium.com/tech-in-asia/material-design-why-the-floating-action-button-is-bad-ux-design-acd5b32c5ef ) but in this case it would be good I think.

From a usability perspective maybe we could display a save button below each category and save the specific setting on click via ajax and show notification on success/error. It keeps mouse movements short and the action button would be close to the settings so it's not complicated to find the action button etc. Of course it's more work though

@mattab
Copy link
Member

mattab commented Oct 2, 2015

From a usability perspective maybe we could display a save button below each category and save the specific setting on click via ajax and show notification on success/error. It keeps mouse movements short and the action button would be close to the settings so it's not complicated to find the action button etc. Of course it's more work though

If we do this there could be an overload of "Save" buttons...

If we're not sure about this one, let's move it back to Short term.

@tsteur
Copy link
Member

tsteur commented Oct 2, 2015

I don't think there would be too many save buttons as each section is quite long anyway, would have to test it. Maybe there's an even better solution... or maybe we can actually split it into different pages etc.

@tsteur
Copy link
Member

tsteur commented Oct 2, 2015

We should move it back to Short term maybe as it takes some time to think about a proper solution and possibly we'd even have to implement different solution to see which one works best. Eg to see whether there would be too many save buttons or not, whether settings could be managed differently better etc

@mattab mattab modified the milestones: Short term, 2.15.0 Oct 2, 2015
@sgiehl
Copy link
Member

sgiehl commented Jun 2, 2017

Guess we can close this one? There is now a save button for each section, which should be good enough imho

@tsteur
Copy link
Member

tsteur commented Jun 2, 2017

👍

@tsteur tsteur closed this as completed Jun 2, 2017
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label Sep 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Milestone
Backlog (Help wanted)
Development

No branches or pull requests
4 participants
@tsteur @mattab @sgiehl @rivadav