UX Feedback: Trash Icon Behavior When Removing Packages from an Environment #6725
gupta-sahil01
started this conversation in
General
Replies: 1 comment 13 replies
|
This design was intentional to allow users to add and remove packages in a single editing session, with all changes only being applied after clicking Save. I agree that this behavior may not be immediately obvious at first. Rather than introducing checkboxes and a separate delete action, maybe we could make the delete icon toggle its state and add a small note near the Save button indicating that changes are not applied until Save is pressed. I think adding checkboxes would make the UI more cluttered and potentially more confusing. |
13 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I wanted to raise a small UX concern I noticed when managing packages in an environment.
When you click the trash icon next to a package, it gets marked (turns red) rather than being removed from the list immediately. The deletion only takes effect after hitting "Save." While I understand this may be intentional to allow batch deletions before committing changes, the trash icon pattern typically implies immediate removal in most UI contexts — so this behavior was a bit confusing at first.
Suggested alternative:
If the intended behavior is to stage deletions before saving, it might be worth considering replacing the trash icons with checkboxes and adding a single "Delete Selected" button alongside the existing "Save" button. This would more clearly communicate to the user that they are marking items for deletion rather than removing them on the spot.
Happy to discuss further or help with a PR if this is something worth exploring. Attaching a screenshot for reference.
My suggestion:
All reactions