4 ms·
once configured, I have always had my settings honored totally different experience, FF ESR decided to update itself just the other day and break a bunch of st
by a_imho 3y ago
once configured, I have always had my settings honored
totally different experience, FF ESR decided to update itself just the other day and break a bunch of stuff out of the blue, because of course moz://a knows better what I need and when I need it. It is very sad people like me need to put up with this abusive behaviour because the alternatives are worse
- kemotep 3y agoDo you have an example? I would like to double check my own browser to see if anything has been changed without my knowledge or permission.
- a_imho 3y agoYou mean besides the forced update? Unfortunately not much I can help with, in my case I was deliberately running ESR 78.14.0 which was force updated to ESR 102.11.0 on May 26 and later 102.12.0 on June 20 (setting is obviously 'Check for updates'). It was a pretty big change first, so I naturally tried to revert back as much as I could. However for example Google Image Search is broken again, clicking it simply crashes the tab (Gah. Your tab just crashed), which could be fixed by tweaking some options in the earlier version iirc. Unless moz://a managed to break it a different way this time