I have a collection containing 4 images and I have the lighttable (file manager) set to display 4 images per row. When I initially open darktable all of the four images in my collection are displayed together on the top row.

If I double-click, say, the second image to go into the darkroom and then exit back to the lighttable the layout changes (presumably with the aim to put the selected image to the top-left of the screen):

If I scroll up, I now have empty space in the first three slots of the lighttable view:

If I scroll up again, the layout changes back to the starting point (all four images on a line together).
Rather than try to place the selected image in the top-left, perhaps the lighttable should merely attempt to place the selected image on the top _row_, thus keeping the overall layout intact.
All I can say is that's the intended behavior, so that's more a feature request than an issue.
Now for the question if that should change, I admit that I have no clear opinion here...
that's more a feature request than an issue
Ok fair enough. Given that it'll reflow when you scroll to the top imo it would be better to not have a different layout when re-entering than before going to the darkroom. And it does feel like a glitch when it reflows to fill the gaps.
This issue did not get any activity in the past 30 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
This seems fixed in https://github.com/darktable-org/darktable/pull/5605
Issue still occurs in 3.1.0+2475~g08eba104b
If this is intended behavior, I find this nothing short of bizarre to have as a default behavior...
I would consider this severe enough, that it should be considered a release blocker for 3.2.0
I would consider this severe enough, that it should be considered a release blocker for 3.2.0
Blocker ? No certainly not. Something to fix probably.
Blocker ? No certainly not. Something to fix probably.
It's your call ofcourse, but it's a significant behavioral regression in an extremely common used part of the application, in the simplest of usecases.
Issue happens on 3.2 branch as well as on master (and is a bit iffy)
I can confirm that this issue is quite annoying - I am editing my pictures from my summer vacation, and the pictures constantly change position... I am on the current git branch, at it is definitely still an issue.
I briefly tested elstoc patch, and that makes it much better, though it's not a full fix. So even with that patch being a huge improvement over what 3.2 currently is, the remaining behavior is still a significant usability regression over previous versions of darktable.
It's difficult to argue that the scroll-up glitch isn't a bug.
But the rest feels to me like just a change in functionality that you can either agree or disagree with. I think it seems fairly reasonable to have the last-edited image appear in the top row, especially given that you could have changed image while in the darkroom.
Most helpful comment
Ok fair enough. Given that it'll reflow when you scroll to the top imo it would be better to not have a different layout when re-entering than before going to the darkroom. And it does feel like a glitch when it reflows to fill the gaps.