app.update.doorhanger and app.update.silent don't work
Categories
(Toolkit :: Application Update, defect)
Tracking
()
People
(Reporter: x-lw-x, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
Went to about:config and changed app.update.doorhanger to false and app.update.silent to true
Actual results:
When a new version came out (69.0.3) I got an update notification that wouldn't go away.
Expected results:
Shouldn't have gotten any update notification with those two settings.
Instead I keep getting update notifications a few times per day which is unacceptable and had to completely disable updates through policies.json which makes my browser vulnerable as it also disables updates through Help -> About and I'm not going to edit the policy every time I need to update or go to the site and manually download the new version from there (those extra steps are also unacceptable, compared to the old way).
In other words instead of keeping me up-to-date this change only stops me from updating regularly every few months and makes me update the browser only if a site stops working with the current version which might take years.
A few versions before these settings were working as intended and the result was that I got no update notifications but went to Help -> About and updated when I had the opportunity (my browser has hundreds of open tabs and needs to run for weeks or months without being restarted, and those daily notification updates are simply unacceptable).
|
||
Comment 1•6 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
||
Comment 2•6 years ago
|
||
Both of those preferences were intentionally removed and product management decided that it should not be possible to disable updates.
There is bug 1557660 where this decision will hopefully be evaluated when there are resources available to do so.
And how exactly does this benefit people like me who want or need to update but on their own schedule?!?!
What was so broken with the previous way of doing things that you had to remove it?
In other words your product management people are giving us a huge middle finger and telling us to f*ck off without any logical reason!
Thought Firefox was the browser for people who like to tinker with stuff? In your pursuit of attracting Chrome users you're trying really hard to get rid of the ones that actually stuck with your product through the years...
So far you're supporting at least 4 versions of Firefox I can think of - the main, the nightly, ESR and the developer edition - why not just add another one with all the options for people who actually need and use them, and change the main one to have no options at all and everything is controlled by you since this is the general direction you're headed anyway.
Don't get me wrong - I don't care that this is removed from the general options page... but if you really cared about people's security you would've just left it at that... instead forcing us to use the policies.json which disables updates through Help->About makes us the opposite of secure, which proves that you don't care about our security at all...
As for the bug you referred to - from what I gather you're talking about policies.json there but this doesn't behave like the old option at all... also as far as I know this file is removed on each upgrade which makes it much more inconvenient solution than the preferences in about:config
|
|
||
Comment 4•6 years ago
|
||
(In reply to LW from comment #3)
And how exactly does this benefit people like me who want or need to update but on their own schedule?!?!
It doesn't
What was so broken with the previous way of doing things that you had to remove it?
There were people that weren't updating due to not knowing they had this preference set.
I hope that this can be improved and hopefully we will be allocated time / resources to do so.
(In reply to Robert Strong [:rstrong] (Robert they/them - use needinfo to contact me) from comment #4)
There were people that weren't updating due to not knowing they had this preference set.
I'm pretty sure those people barely know how to turn on their PC let alone tinker in about:config and we shouldn't be the ones punished for their ignorance.
That's a "great" example you're setting up here - if you're lazy or stupid, you'll be rewarded, otherwise you'll be punished...
As I said above - I don't care if something gets removed from the general options... you can leave there only one or two settings just for the twelve-o-clock flashers for all I care, but when someone uses about:config it's a sign that they're at least partially aware of what they're doing and whatever they do there is their own responsibility, not yours and shouldn't be stopped... otherwise you can just remove about:config altogether if you want complete control over the way people use your product...
I hope that this can be improved and hopefully we will be allocated time / resources to do so.
I still consider this a bug that needs fixing and not something that needs improvement as it was already working fine when version 63 came out - missing setting in the general options and working settings in about:config so people who know what they're doing can update when they decide to...
(In reply to Robert Strong [:rstrong] (Robert they/them - use needinfo to contact me) from comment #4)
There were people that weren't updating due to not knowing they had this preference set.
I'm pretty sure those people barely know how to turn on their PC let alone tinker in about:config and we shouldn't be the ones punished for their ignorance.
That's a "great" example you're setting up here - if you're lazy or stupid, you'll be rewarded, otherwise you'll be punished...
As I said above - I don't care if something gets removed from the general options... you can leave there only one or two settings just for the twelve-o-clock flashers for all I care, but when someone uses about:config it's a sign that they're at least partially aware of what they're doing and whatever they do there is their own responsibility, not yours and shouldn't be stopped... otherwise you can just remove about:config altogether if you want complete control over the way people use your product...
I hope that this can be improved and hopefully we will be allocated time / resources to do so.
I still consider this a bug that needs fixing and not something that needs improvement as it was already working fine when version 63 came out - missing setting in the general options and working settings in about:config so people who know what they're doing can update when they decide to...
P.S. Someone please delete my previous comment as I have skipped to add a few new lines...
|
|
||
Comment 7•6 years ago
|
||
You can discuss this further in the newsgroups / mailing lists... as far as this bug is concerned it is an intentional decision by product management and discussing this in this bug isn't going to change that decision. I've asked for time / resources from product management to deal with this but it isn't a high enough priority over other work at this time.
Well, you can thank your product management from me for managing to make me switch ships after 12 years of using your product...
I've tried your forums, I've tried the feedback features built in the browser, I've even tried here... and apparently it's all pointless and a complete waste of my time... should've just switched to Basilisk ever since your bosses (or whatever they are) decided to brake things... it might be unstable and crashing from time to time but at least it doesn't put me in a state of rage which is the exact result of those update nags...
Description
•