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
File list wrongly sorted when inserting new elements when hidden elements present #25309
Comments
Now looking at the hidden files implementation, it seems to do a lot of gymnastics. Then toggling between showing hidden files and not hidden files would just be a matter of toggling a CSS class on the table element. |
Anyway, in the future I'd like to look into making the FileList use the Backbone approach, which would need rewriting a lot of logic anyway. |
It's even worse than I thought. In the past there was a one to one index mapping between "tr" elements and Have four entries:
Delete "abc". But the index is shifted, so it deletes another one and |
WIP PR here #25846 |
Fix is here #25856 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Steps
Expected result
Order is: "abc", "def"
Actual
Order is: "def", "abc" until refresh.
Version
9.1.0RC1
The problem is that the code that inserts new elements into the list calculates the insertion index. That routine seems to not properly cope with hidden elements.
CC @ChristophWurst
The text was updated successfully, but these errors were encountered: