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
Widgets that use ListViewFilter "forget" selected variables filtered out while searched. Watch the video below. In the console, I print selections. When a variable is filtered out by searching, it also gets removed from the setting, and a commit is called.
Screen.Recording.2024-03-20.at.16.01.46.mov
For example, when Petal length and width variables are selected, they get unselected when they are filtered out from the view.
I would expect the variable would still be selected as it was in the deprecated ListViewSearch
How can we reproduce the problem?
Use a unique widget. Select petal length and width. Start typing "sepal" and then remove the filter. Previously selected variables are no longer selected.
The text was updated successfully, but these errors were encountered:
janezd
added
bug
A bug confirmed by the core team
and removed
bug report
Bug is reported by user, not yet confirmed by the core team
labels
Mar 22, 2024
What's wrong?
Widgets that use ListViewFilter "forget" selected variables filtered out while searched. Watch the video below. In the console, I print selections. When a variable is filtered out by searching, it also gets removed from the setting, and a commit is called.
Screen.Recording.2024-03-20.at.16.01.46.mov
For example, when Petal length and width variables are selected, they get unselected when they are filtered out from the view.
I would expect the variable would still be selected as it was in the deprecated ListViewSearch
How can we reproduce the problem?
Use a unique widget. Select petal length and width. Start typing "sepal" and then remove the filter. Previously selected variables are no longer selected.
The text was updated successfully, but these errors were encountered: