3 ms·
not sure about Chrome, but you can turn off update on Firefox. I do this, and for good reason. I dont like the constant churn of browser UI moving around and ch
by 2h 3y ago
not sure about Chrome, but you can turn off update on Firefox. I do this, and for good reason. I dont like the constant churn of browser UI moving around and changing every few months.
So users in that situation should not be punished by web devs who only support the bleeding edge browser versions.
- crazygringo 3y agoThen that's on you. When 90% of users are on the newest version within a couple weeks, that's not "bleeding edge". It's mainstream. You're also opening yourself up to security vulnerabilities as you browse. If you turn off auto update, it's up to you to accept the consequences of both security risks and of sites breaking.
- 2h 3y ago> Then that's on you. you say that like I am the only person who does this. > When 90% of users are on the newest version within a couple weeks, that's not "bleeding edge". [citation needed]
- akarlsten 3y ago> you say that like I am the only person who does this. Essentially, yes: https://caniuse.com/usage-table https://caniuse.com/usage-table
- 2h 3y ago2.7% of ALL browser usage is still a significant number, and certainly more than one person.
- superkuh 3y agocaniuse uses statscounter. It's really no surprise that statistics collected via javascript fail to include browsers that aren't executing it or don't have the modern JS "features" it uses. https://en.wikipedia.org/wiki/Streetlight_effect https://en.wikipedia.org/wiki/Streetlight_effect
- orhmeh09 3y agoWeb devs should not punish such users, agreed. Who will pay extra on top of the hourly rate to address the needs you have? Especially when it's your problem with somebody else's software (Firefox) that would require this extra investment.
- 2h 3y agoits not a problem with the software, its a problem with the web site adding features that only work with the newest browser, without any fallback for older browsers.