You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was just playing around on the demo of <AccordionGroup>
Enable 'allowMultiple'
Open >1 Accordions
Disable 'allowMultiple'
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
The text was updated successfully, but these errors were encountered:
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.
I was just playing around on the demo of
<AccordionGroup>
-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
The text was updated successfully, but these errors were encountered: