Timeline for Supported browser versions needs update
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 5, 2023 at 10:58 | comment | added | giamir StaffMod | I have changed the status to [status-deferred]. We have created a task in our team's backlog to automate these deployments on a daily cadence. We should be able to get to it in the next few weeks. Thanks for your patience. | |
| Aug 13, 2023 at 0:12 | comment | added | Elements In Space | It's been a few weeks since my last comment. This issue has not been fixed, and it's incorrect that this bug report is tagged [status-complete]. So, I am unaccepting this answer. | |
| Jul 19, 2023 at 9:24 | comment | added | Elements In Space | It's been only a few months, and the list of latest browser versions is about 5 whole version numbers out of date. But I don't mind keeping this as the accepted answer if you can correct the first sentence (to "temporarily fixed" or similar), and change the tag from [status-complete] to [status-deferred]. | |
| Mar 4, 2023 at 18:47 | comment | added | Shadow Wizard | Since the "completed" status won't be relevant in few weeks, also maybe better put it as status-deferred and change to completed if and when it is actually automated? | |
| Mar 4, 2023 at 18:44 | comment | added | Shadow Wizard | Sorry but there's no way this will be updated often. Until it's automated it's useless to have this page. Nothing personal, you're doing great job with your limited time, and so each and every developer. But in this case, it's the system that is basically broken. (In the few months it will take until someone will notice, post another bug report, and a dev will push the change, browsers will get lots of new versions.) | |
| Mar 3, 2023 at 14:34 | comment | added | Ben Kelly StaffMod | @Makyen Good idea! I very quickly added the "last generated on" date to the footer, next to the different package versions we're using. I agree that we could also add a disclaimer there to make it more obvious, but I think this approach is good enough for the short term. I may take an hour or so today to see if I can't (safely) autoupdate those dependencies using GH Actions. | |
| Mar 3, 2023 at 0:20 | vote | accept | Elements In Space | ||
| Aug 13, 2023 at 0:12 | |||||
| Mar 2, 2023 at 22:26 | comment | added | Makyen | If you don't have automatic updates that happen often, then perhaps add wording to that pagesaying that the listed version numbers are as of a specific date, but that the browser version numbers which are actually supported may have changed as a result of a browser's later releases. It would also be good to link to pages from each browser manufacturer which show the versions which are actually current. Right now, that page becoming outdated makes the Stacks project, and Stack Overflow in general, appear to be a bit neglected. | |
| Mar 2, 2023 at 22:17 | history | answered | Ben KellyStaffMod | CC BY-SA 4.0 |