Search Issue Tracker
By Design
Votes
0
Found in [Package]
3.14.2
Issue ID
HUBX-1503
Regression
No
Unclear Modules cancellation description in "Cancel download" modal window in Unity Hub
Steps to reproduce:
1. Open Unity Hub
2. Select "Installs" tab
3. In Installs window press on "Manage" button on any version (for example 6000.2.7f1)
4. From the dropdown menu select "Add modules"
5. Scroll down, select Documentation Module
6. Press "Install"
7. At the top bar press "Installs" button
8. In the dropdown menu, below Editor version, press on "X" button to cancel pending items
9. When "Cancel download?" modal opens, observe the modal description
Actual results: "Cancel download?" modal only shows "Unity 6 (6000.3.0a1)" text in description
Expected results: "Cancel download?" modal description should show what modal or modals are being cancelled in the description, not only Editor version, which could be confusing for the user
Reproducible with versions: 3.14.2
Tested on (OS): Windows 11
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
The current copy in the “Cancel download?” modal was updated in a previous ticket to make the action clear and consistent. The modal intentionally refers to the main Editor version because the cancellation action applies to the entire pending installation initiated by the user. Since the user explicitly chooses to cancel from the install queue, this wording is considered sufficient and aligned with the current UX decisions.