I agree that only supporting the latest browser releases is entirely reasonable. I'm a bit surprised tho, that you don't make best effort accommodations for extended/long-term support releases, especially since there are popular among institutional users, which likely strongly overlap with your audience.
One the topic of Firefox 128 (& 115) ESR, you are right their support is about to expire on 9/16 and the successor (140) supports the feature in question.
I understand that you don't want to accrue technical dept, in the form of soon-to-be entirely useless polyfills, especially since this is quite bothersome to keep track of.
I won't lament this being a Won't Fix and will instead bother our IT department about their choice on browser update cycle.
Benjamin Fischer on 14/Jul/25 11:42
Hi mflorea,
thanks for the quick and detailed reply.
I agree that only supporting the latest browser releases is entirely reasonable. I'm a bit surprised tho, that you don't make best effort accommodations for extended/long-term support releases, especially since there are popular among institutional users, which likely strongly overlap with your audience.
One the topic of Firefox 128 (& 115) ESR, you are right their support is about to expire on 9/16 and the successor (140) supports the feature in question.
I understand that you don't want to accrue technical dept, in the form of soon-to-be entirely useless polyfills, especially since this is quite bothersome to keep track of.
I won't lament this being a Won't Fix and will instead bother our IT department about their choice on browser update cycle.
Benjamin Fischer on 14/Jul/25 11:44
Hi mflorea,
thanks for the quick and detailed reply.
I agree that only supporting the latest browser releases is entirely reasonable. I'm a bit surprised tho, that you don't make best effort accommodations for extended/long-term support releases, especially since there are popular among institutional users, which likely strongly overlap with your audience.
One the topic of Firefox 128 (& 115) ESR, you are right their support is about to expire on 9/16 anyway and the successor (140) supports the feature in question.
I understand that you don't want to accrue technical dept, in the form of soon-to-be entirely useless polyfills, especially since this is quite bothersome to keep track of.
I won't lament this being a Won't Fix and will instead bother our IT department about their choice on browser update cycle.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
