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

User should not have to guess which part of a drive string will, when clicked, open the drive and which part will eject the drive #3464

Open
LinuxOnTheDesktop opened this issue Sep 30, 2024 · 0 comments

Comments

@LinuxOnTheDesktop
Copy link

Distribution

Mint 22

Package version

6.2.8

Frequency

Always

Bug description

Nemo shows USB devices thusly: <user-given label of device)> - and, perhaps somewhat confusingly, there is a thin 'space used' line underneath all of that. Here is a photograph:

image

(I am sorry for the bad photograph. I am still in the process of setting up my system - I have not finished setting up passwords and integration with my other computers. I am trying to set those things up.)

The whole string has the same tooltip and there is no box around the eject icon. Thus the user does not know just where within the string a click will cause an ejection attempt as against a mounting or (more precisely) a viewing attempt. Obviously the user has something to go on. Equally clear is that the user should not have to worry about where the cut-off point is. Evidently this is bad UX.

Steps to reproduce

  1. Have USB drive mounted.
  2. Have a need to either view the contents of the device or to eject the device.
  3. Worry, at least a bit or for a moment - thus, at best, being slowed down - how one achieves the one rather than the other.

Expected behavior

The solution is to put some sort of box around the ejection icon when that icon is moused-over and - or at the least - to change the tooltip when ejection is going to be what happens.

Additional information

Often, transferring data via USB is not the best way to do things. Yet, when one yet to set-up up a network or set-up cloud storage, then needs must. In that situation, one wants as few headaches as possible.

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

1 participant