Usually they’re building the website with browserlist and polyfills, and they specify how old a browser they wish to support, usually by analysing percentages of public usage, or they allow types only supported in newer browsers. Meaning if they use a feature only available in newer browsers, then it won’t be automatically backported to support older browsers.
But that’s only if they actually use those features, they’re just available to them. And it’ll only break in those places they do use them, which could be quite little of the site.
So often it’s just “we can’t guarantee it’ll work in your old browser and enough of our users use newer browsers that we’ll block you and not care”.
yupp, and i hate that. i use a firefox version that don’t supports private fields, and because a common js lib uses them a lot of websites suddenly stopped working for me just because of this bs. instead of just using a normal variable they use private fields and kill a ton of older browsers by doing so. and most website owners don’t care so asking them just leads to them saying “just upgrade bro”.
I’m a nerd and programmer and active in the security sector, so i know how to protect myself from malware and stuff (i know, it sounds naive). i have tons of browser addons who block malicious things and protect me and even wrote my own plugins for firefox to do certain stuff. the newer firefox browsers are implementing more and more forced features you can’t disable i dislike, so I don’t want to update. updates changes all the time stuff i need or want and force features nobody actually needs, and there is no way anymore to disable those manually. so I don’t update to those versions anymore as long as possible. it’s the same with windows updates who introduce new features nobody wants or which removes stuff you need… it’s just annoying.
I don’t want to get forced to use a specific UI i dislike or to have features removed or added i need or dislike.
usually it starts with “we let you disable it still with about:config”, but then in later versions they kill it off so the variables don’t do anything anymore. then they remove it completly in even later versions.
Usually they’re building the website with browserlist and polyfills, and they specify how old a browser they wish to support, usually by analysing percentages of public usage, or they allow types only supported in newer browsers. Meaning if they use a feature only available in newer browsers, then it won’t be automatically backported to support older browsers.
But that’s only if they actually use those features, they’re just available to them. And it’ll only break in those places they do use them, which could be quite little of the site.
So often it’s just “we can’t guarantee it’ll work in your old browser and enough of our users use newer browsers that we’ll block you and not care”.
yupp, and i hate that. i use a firefox version that don’t supports private fields, and because a common js lib uses them a lot of websites suddenly stopped working for me just because of this bs. instead of just using a normal variable they use private fields and kill a ton of older browsers by doing so. and most website owners don’t care so asking them just leads to them saying “just upgrade bro”.
Man, javascript is starting to turn into java, isn’t it? They added encapsulation. What else they’re going to add?
Why? I feel like a browser is something you’d definitely want to keep up to date for security reasons if given the option.
I’m a nerd and programmer and active in the security sector, so i know how to protect myself from malware and stuff (i know, it sounds naive). i have tons of browser addons who block malicious things and protect me and even wrote my own plugins for firefox to do certain stuff. the newer firefox browsers are implementing more and more forced features you can’t disable i dislike, so I don’t want to update. updates changes all the time stuff i need or want and force features nobody actually needs, and there is no way anymore to disable those manually. so I don’t update to those versions anymore as long as possible. it’s the same with windows updates who introduce new features nobody wants or which removes stuff you need… it’s just annoying.
I don’t want to get forced to use a specific UI i dislike or to have features removed or added i need or dislike.
Not even through
about:config?nope, not even with about:config.
usually it starts with “we let you disable it still with about:config”, but then in later versions they kill it off so the variables don’t do anything anymore. then they remove it completly in even later versions.