Closed navidhegan closed 2 months ago
Apologies, this seems pretty petty reading it back, am hoping it will enhance the user experience
I should add that the back button would return the user to the list of Collections
Maybe we could have a button to see the collections directly in the menu?
the arrow is not a back button, it's an upper level button:
Collections and readlists are top level items, they don't belong in a particular library.
If you want to go back, use your browser's back button.
Wouldn't the list of collections be the top level item, so a return from the collection to the list of collections makes sense.
If you're using a touch interface switching from it to having to use the browser controls is jarring.
When you're in a collection you're missing the controls to switch between 'recommended, browse, collections, read lists', so it acts as a dead end.
When you're in a collection you're missing the controls to switch between 'recommended, browse, collections, read lists', so it acts as a dead end.
those are Library level controls, when you are in a collection those don't make sense in the current context anymore
I think maybe I'm using Collections incorrectly, at the moment I'm using it to represent what used to be my folder structure on a harddrive (i.e. grouping together comics relating to Aliens, Avengers, Venom, etc), I need to embrace using the metadata to perform the same task... though might mean I need to investigate adding tags to my collection or something.
If you think there doesn't need to be a back button that's okay, just thought I'd ask/explain my thinking. Thanks for hearing me out :)
Steps to reproduce
Expected behavior
Expectation that there be a 'back' button similar to the one provided when entering a series, allowing a return to the previous screen using a mouse click:
Actual behavior
In a collection there is no back button, so returning to the previous screen is either by pressing back on the browser, or returning to the top level 'Library' using the navigation tree structure on the left (that may be closed).
I realise this may be by design, but hear me out, up until entering a Collection all navigation can be completed seamlessly simply clicking with the left navigation panel hidden...
A typical User experience (arguably) is that clicking back on a browser is undesirable as it can cause issues reloading a page, so returning to a previous page requires the left navigation panel and a return to the top level navigation for the library, introducing several clicks if you prefer to keep the left navigation hidden.
Logs
No response
Komga version
v1.11.3-master
Operating system
Ubuntu 24.04 LTS (GNU/Linux 6.8.0-39-generic x86_64)
Installation method
Docker
Other details
No response
Acknowledgements