Skip to content
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

[Feature Request] Dedicated Back or Close button #774

Open
anandhu2311c opened this issue Nov 22, 2024 · 4 comments
Open

[Feature Request] Dedicated Back or Close button #774

anandhu2311c opened this issue Nov 22, 2024 · 4 comments

Comments

@anandhu2311c
Copy link

Currently, when a file is opened in the file manager, there is no dedicated back or close button. Users can only navigate back using the file path, which is not an intuitive experience. To improve user navigation, it would be beneficial to add a specific Back button that allows users to return to the previous directory, and a Close button that closes the current file and returns the user to the file manager's main interface. These buttons should be easily accessible, with the Back button placed near the top left and the Close button near the top right of the file viewer. This enhancement will make the file manager more user-friendly and efficient for navigating between files and directories.

@anandhu2311c anandhu2311c changed the title [Feature Request] [Feature Request] Dedicated Back or Close button Nov 26, 2024
@mickael-kerjean
Copy link
Owner

Why not using the browser back button? I've spent hours to make sure Filestash wouldn't break the native back button, I don't see how adding yet another button that does the same thing being an improvement?

@anandhu2311c
Copy link
Author

I understand and appreciate the effort you've put into ensuring the browser’s back button works seamlessly. However, adding dedicated back and close buttons could still improve user experience. Many users, especially those less tech-savvy, might not realize they can use the browser’s back button for navigation. Dedicated buttons in the interface improve discoverability and align with user expectations, as most file managers have visible navigation controls. They also provide a consistent and context-specific way to navigate without relying on browser controls, which can sometimes be ambiguous, especially when users open multiple tabs or links. Additionally, dedicated buttons allow customization, such as a Back button navigating to the parent directory or a Close button returning directly to the home directory, improving workflow efficiency. On mobile devices, where browser back buttons can interfere with system navigation, in-app buttons enhance usability. While the browser back button is functional, these additions aim to make the file manager more accessible and user-friendly.

@mickael-kerjean
Copy link
Owner

mickael-kerjean commented Dec 16, 2024

I'm not convinced everyone would see this as an improvement. Personally I see those buttons as "bloat" as it's very easy to endup with a software that look like the cockpit of an A380 and introducing that kind of buttons would be a step in that direction. As such the best place for such feature would be in a plugin so that people with different opinion could have this enable or not depending on their preference.

@anandhu2311c
Copy link
Author

Okay understood.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants