Disable the close button in the stub during the installing phase
Categories
(Firefox :: Installer, defect, P3)
Tracking
()
People
(Reporter: vlucaci, Unassigned)
Details
Attachments
(1 file)
3.33 MB,
image/gif
|
Details |
Affected versions
- 69.0a1(2018/05/23)
- 68.0b4
- 66.0a1(2018/12/31)
Affected platforms
- Windows 10x64
- Windows 7x64
- Windows 8.1x64
Steps to reproduce
- Install FF via installer.
- Let the progress bar reach around 60-70%.
- Click on the X button from the installer.
Regression range
- Will return with regression ASAP.
Expected result
- The progress of the installation is paused, the cancel confirmation prompt is displayed alongside with its audio notification correspondent.
Actual result
- The progress of the installation continues, the audio notification is triggered, the confirmation prompt is not displayed.
Additional notes
- The moment in which the user clicks X to cancel the installation , the cancel confirmation prompt must be displayed and progress paused regardless of the position of the progress bar.
Comment 1•5 years ago
|
||
This behavior is unfortunate, but intended. The first 60% of the progress bar is the download of the full installer, and that can be stopped at any time. But after we start actually running the full installer, there's no way to stop it without leaving the system in some inconsistent state, because it isn't capable of rolling back whatever actions it's already taken. So all we can really do is disable cancelling the installation from that point.
Updated•5 years ago
|
Reporter | ||
Comment 2•5 years ago
|
||
Hello Matt,
As you stated, this behavior is very unfortunate.
As a (normal) user, I expect that whenever I want to cancel the installation process by clicking X , then the process will be terminated, or paused at the very least.
I agree with the suggestion about removing the possibility of cancelling the installation from that point. Maybe removing the possibility to interact with the X button entirely (making it grayed out after that point, but in this case I would suggest to inform the user in a small message in the UI).
Should I open a different issue for this*(or maybe an enhancement ticket)?
Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 3•5 years ago
|
||
That's a good idea, there might be something we can do to gray out the close button. It won't be a high priority, but it's worth considering when we get a chance.
Updated•2 years ago
|
Description
•