![]() mostly I just have questions not answers though. So about 2.5 years ago.īut this does make me re-think what appropriate browser support policy should be. When did that come out? Looks like July 20 2019. Version 76 is what his mom's chromebook had. (At what point would the OP author think we could stop transpiling down to ES5? Literally never?) Where do we draw the line? Most tools oriented towards helping you do legacy browser support (like caniuse) don't even have UI's oriented toward helping you figure out what version of Chrome is when and where a good line to draw might be. I'm not sure how likely that is to happen. They should be making their website’s code more accessible to legacy devices. ![]() > This is a problem with the people who make that website. ![]() Should we be trying to support old versions of Chrome? The author thinks so. As a web dev, I had been thinking "there's no reason anyone would be running anything but the latest version of Chrome" - but here's a reason. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |