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
in some special cases for multiple selection when we use setSelectedItems instead of addSelectedItem, it can happen that previousSelectedItemsRef.current is not updated because setSelectedItems sets the same amount of items but different.
Example
1, 2, 3, 4
set 2, 3
set 1, 4
but in previousSelectedItemsRef.current are still 2, 3
set 1, 2, 3
in previousSelectedItemsRef.current are 1,2,3 because length changed
The text was updated successfully, but these errors were encountered:
It is a corner case, but still valid. On the other hand, the alternative would be to search for potentially removed items on every render. Any better suggestions?
Furthermore, this hook logic is to announce to screen readers when an item is removed. It needs a completely different logic in order to handle the case with setSelectedItems.
I am still thinking about a better way with the whole a11y screen reader announcements, since the current behaviour is not great. I will update once we figure out something.
downshift/src/hooks/useMultipleSelection/index.js
Line 81 in 90d6d72
in some special cases for multiple selection when we use
setSelectedItems
instead of addSelectedItem, it can happen that previousSelectedItemsRef.current is not updated becausesetSelectedItems
sets the same amount of items but different.Example
1, 2, 3, 4
set 2, 3
set 1, 4
but in previousSelectedItemsRef.current are still 2, 3
set 1, 2, 3
in previousSelectedItemsRef.current are 1,2,3 because length changed
The text was updated successfully, but these errors were encountered: