News for hackers. Stuff that matters.
Re:CSS WG resolved to officially work on native custom funct... by JoshTriplett on Tuesday February 13, 2024 @12:45PM (#39360409)
I'm genuinely curious to hear which non-evergreen browsers people are having to support. Niche mobile browsers from ancient Android phones? Some of the more obscure mobile browsers from https://caniuse.com/ciu/comparison , or even more obscure ones that aren't listed there?

To what extent are those platforms unable to support a better browser? For instance, Firefox works all the way back to Android 5.0.

Re:CSS WG resolved to officially work on native custom funct... by reaperducer on Tuesday February 13, 2024 @02:53PM (#39362024)
I'm genuinely curious to hear which non-evergreen browsers people are having to support.

Browsers on devices (sometimes iPads, sometimes Android) that are inside touch-screen kiosks.

Some of the ones I work with are in places so remote, it would take me three or four days to reach them if a software update goes wrong. Then another three or four days to get back to the office.

Re:CSS WG resolved to officially work on native custom funct... by lycos on Tuesday February 13, 2024 @01:01PM (#39360625)
Without even looking up statistics or searching the web the easiest answer for you; ever hear of iOS / iPadOS and how every browser is Safari underneath and not everyone installs update (or uses devices that can't be updated); like elderly people who are also real users? Yet it is also (depending on region) the most popular mobile and tablet platform?

FYI This is my last reply to you, you're just looking to be proven right it's not a useful discussion.

Re:CSS WG resolved to officially work on native custom funct... by JoshTriplett on Tuesday February 13, 2024 @01:20PM (#39360847)
> and not everyone installs update (or uses devices that can't be updated);

That's exactly the kind of example I was looking for, thank you; the idea that people would run iOS and not get Safari updates had not occurred to me, and that's an entirely valid use case and a potentially large user cohort for some sites. Sites with such users would indeed be unable to make immediate use of features just because they're in evergreen browsers. Thanks for the explanation.

I know that there are plenty of people out there who are not looking to change their mind. This was not one of those cases. In this case, I was looking to hear the benefit of the experiences behind your comment of "Some of us need to", and hearing it helped me update from "it's safe to rely on evergreen browsers" to "it may still be necessary for some sites to check statistics on usage of old Safari among their users, and adapt accordingly".