-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Floating file header jumps to top on sorting #15438
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
What should be the expected behaviour btw, if you sort everything, keeping the scrolling position would most likely not show the relevancy the user is looking for? |
This is what I am used to on other file listings, e.g. Dolphin on Linux, or Thunderbird. |
Good from me 🤷♂️ |
🤔 what @skjnldsv said about scrolling to show relevant info makes sense to me as well, on checking other apps it truly is a mixed bag. Windows file explorer and Google Drive scroll on changing sort order, while Dropbox, Nautilus on Ubuntu and the other apps @tobiasKaminsky mentioned don't scroll. I would go with scrolling for same reason @skjnldsv mentioned, ccing @jancborchardt here |
We do a hard refresh on re-sorting, so pretty difficult to keep the position anyway? I would also agree with @skjnldsv and @nimishavijay’s research in that it makes a bit more sense to scroll to top since the whole content changed. A quick animation that scrolls to the top of the list would of course be nice, but yeah with the hard refresh it’s difficult. |
There is some options possible. It's easy to remember the top-to-scroll-position pixel amount, but depending on what we wanna achieve, some stuff can and can't be done :) What about this:
|
Also, keep in mind files to vue is still ongoing, a hard refresh might be avoidable here (just re-rendering might be possible) |
instead it position should remain, but only content should change.
The text was updated successfully, but these errors were encountered: