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

[QUESTION] - Side menu Chevrons pointing left #4110

Closed
ChrisLang opened this issue Dec 6, 2021 · 3 comments
Closed

[QUESTION] - Side menu Chevrons pointing left #4110

ChrisLang opened this issue Dec 6, 2021 · 3 comments

Comments

@ChrisLang
Copy link

ChrisLang commented Dec 6, 2021

Good day,

Could I kindly find out why your chevrons in the side menu point left, this seems to be incorrect to me.
I could very well be incorrect myself, so felt like reaching out.

This component for the side menu is basically a Accordion component.
If you look at how its normally done, they always point down or right when closed and up when open.
https://dribbble.com/search/accordion%20ui%20component

The way I think about it is an arrow pointing left is used when navigating back in time and arrow point right is navigating forward in time.

I've been a designer / developer for almost 15 years and this one is a bit of an eye sore for me, not a biggy as I just think most people will over look it and isn't really breaking any UX.

other useful links I found
https://ux.stackexchange.com/questions/5735/which-way-should-arrows-point-in-a-collapsible-accordion-left-down-down-up
https://www.smashingmagazine.com/2017/06/designing-perfect-accordion-checklist/#:~:text=First%2C%20if%20accordion%20items%20are,plus%20icon%20might%20work%20well.

Cheers 😊

@REJack
Copy link
Collaborator

REJack commented Dec 9, 2021

I understand your point and I had also my problems with it, but in v3 I wont change it to the "normal" behavior. I will change it in v4, may @danny007in will change it in our v4-dev branch.

@danny007in danny007in added this to the v4.0.0 milestone Dec 9, 2021
@ChrisLang
Copy link
Author

ChrisLang commented Dec 10, 2021

@REJack thanks for the feed back, very much appreciated 👌. No rush we'll update outside at some point in in the meantime 👍

@craph
Copy link

craph commented Jun 22, 2022

Hi @REJack , @danny007in ,

I think this issue (Question) can now be closed because you already merged this : #4360 :)

Thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants