-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[UX] Button order in modal #16060
Comments
It could be easily changed to.match but I am not so sure it is needed. In one case they are a toolbar and.in the other they are submit buttons on a form. So to me they are not the same thing so do not have to be consistent but I see no reason to prevent a change either |
Technically, they're the same, just in different places. |
Pinging @andrepereiradasilva since it looks like this was done with #11830 (and related ones) |
I guess no special reason at looking at the original pr. |
@Bakual you are very very unlikely to get a reply from @andrepereiradasilva |
Looks like |
For what it's worth: in the mobile era the dominant buttons tend to lay on the right hand of the screen (easily accessed using one hand), but then again people in the community still believe that the admin area is not for mobiles... |
And that assumes everyone is right handed. It's certainly not easier if you are left handed |
The admin area can be used with mobiles, but more often it is used on desktops. That's not only a believe. |
I am closing this based on the lack of any overwhelming reason to change it. |
Steps to reproduce the issue
Create a menu item "SIngle Article" and click the button to "Create" a new article within it.
Or if you have a multilingual site check the association fields in an item, they have similar buttons.
Expected result
The save buttons in the modal are in a consistent order like in regular forms.
Actual result
The buttons are in reversed order
Regular form:
Modal form:
Additional comments
I don't know if there was a reason to have the buttons in reversed order. I just noticed today and found it a bit unexpected.
The text was updated successfully, but these errors were encountered: