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

UX on <AccordionGroup> 's "allowMultiple" property #13

Open
dennismok2018 opened this issue Apr 29, 2023 · 1 comment
Open

UX on <AccordionGroup> 's "allowMultiple" property #13

dennismok2018 opened this issue Apr 29, 2023 · 1 comment

Comments

@dennismok2018
Copy link

dennismok2018 commented Apr 29, 2023

I was just playing around on the demo of <AccordionGroup>

  1. Enable 'allowMultiple'
  2. Open >1 Accordions
  3. Disable 'allowMultiple'
  4. Now we get 3 behaviours:
    -a : cannot close already opened Accordions
    -b: can open new accordions but newly opened Accordions cannot be closed as the others
    -c: if a newly opened one is the last unopened one on the list, every opened Accordion are then closed and only the last opened one stay open (I think only this intuitively should be the default behaviour after we get rid of 'allowMultiple' and back to default)

P.S. Not sure how one would get there in real-life application except tinkering with the demo like me so might not actually be a bug

@atk
Copy link
Owner

atk commented Apr 29, 2023

Changing the properties while the accordions are rendered is currently considered not a use case. However, I might reconsider this behavior if I get reports of this breaking real-life apps.

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

No branches or pull requests

2 participants