Timeline for Stack Exchange changes broke UI on multiple legacy browsers - Again
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2023 at 20:59 | comment | added | WordPress Speed |
It's amazing that Stack Exchange has privacy concerns about users with legacy devices, but has no concerns about their accessibility. It simply fills up half a 4" device screen with a non-removable popup to keep telling that I concern about your privacy, no matter you can not see the page content. FUNNY!
|
|
| Apr 12, 2022 at 23:24 | comment | added | Marco Bonelli | I think everyone can agree that it doesn't make sense to keep supporting browsers dating back to before I was born. However, supporting just the last two versions of Chrome covers a time-span of less than 6 months. It doesn't make sense to me to be honest. Seems like way too little time. And for what? To be able to use the latest CSS flex style attribute? Come on... | |
| Apr 10, 2022 at 6:58 | comment | added | Shadow Wizard | "reasonable point not to support old browsers" - easier development, no need to check every line if it's supported by all browsers. Saves lots of hours, and in theory enable them to make bigger things. (Assuming over time JS offer more features.) | |
| Apr 9, 2022 at 8:15 | history | edited | Journeyman GeekMod | CC BY-SA 4.0 |
added 201 characters in body
|
| Apr 9, 2022 at 7:45 | history | answered | Journeyman GeekMod | CC BY-SA 4.0 |