4 ms·
Could they stop disabling the browser when it updates (running against the about:config settings) so that I don't lose work when I have a partially functional b
by smeagull 4y ago
Could they stop disabling the browser when it updates (running against the about:config settings) so that I don't lose work when I have a partially functional browser that won't load new pages which breaks every single page application?
- lucb1e 4y ago> a partially functional browser that won't load new pages I thought it was just me because it was going on for so long! Since maybe half a year, every time you use Firefox for a while (I suspend to RAM when not using my system), it starts to cheerfully go "whoops, this tab has crashed!" or "We need just one tiny thing to keep going [nuke¹ and restart whole browser as the only button]". Makes me want to firewall mozilla IP ranges and subscribe to an rss feed to see when a security release came out so that I can go to the update menu manually and do it not when I am in the middle of looking something up during a phone call with someone. It's also not as though this uses the regular updates mechanism. There is still Menu -> About -> "you're up to date" / "click here to download update" / "click here to restart to apply update" and it will also notify you of those releases. This is some other mechanism going on under the hood. Perhaps the Experiments thing that gets randomly deployed to random people's browsers, not sure, I thought I disabled all of that years ago. ¹Yes I know firefox and other browsers nowadays have this textarea/input content restoring and such. Ask me how well that works now that every developer decided they're too cool for basic HTML elements whose functionality have been honed for close to three decades now, and would rather re-invent everything from page loading to input fields by using dynamic javascript instead.