Updating with a package manager breaks user experience
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: a.viamontes.esquivel, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
I was typing a search (in the search bar), in the middle of something that really required concentration, and Firefox refused to do anything saying that it needed to update itself.
Actual results:
Despite my best fiddling with disabling auto-updates, including the settings in the "about:config" page, I couldn't get Firefox to leave the insulting auto-update screen. I had to give up and lost all the tabs a big chunk of time.
Expected results:
Firefox can wait until I close it or the computer starts for it to use his newest-newy bunch of thingies. Or are Firefox devs so self-centered that they don't realize that what other people do is important sometimes?
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
Also, for the record, my computer was restarted yesterday, so this means whatever timer functionality is built into this strike-and-update feature is pretty anxious.
Comment 2•6 years ago
|
||
when you're using a distro provided builds and the package manager is updating firefox, the timing of updates is not within firefox' control.
the timing of updates is not within firefox' control
That doesn't mean firefox should require a restart. Chrome doesn't require me to restart chrome when my package manager updates it, or any other program that I know of for that matter.
Updated•6 years ago
|
![]() |
||
Comment 5•6 years ago
|
||
Package manager updates have nothing to do with Toolkit -> Application Update so moving back to untriaged so this can be moved to the correct component.
Comment 9•4 years ago
|
||
I guess this is not going to get fixed.
Description
•