DEV Community

Discussion on: A Non-Business Case for Supporting Old Browsers

Collapse
 
nylen profile image
James Nylen

Especially for complicated, JS-driven sites, the only way to make sure they keep working in IE 11 is to make testing in IE 11 part of the regular development process.

This is infeasible for many people who don't have the resources (time, or access to the browsers in question) to maintain an ever-growing list of supported browsers.

I prefer to set a policy where modern browsers are officially supported, and try not to rely on large amounts of JavaScript for key functionality of the site. However, this is not always possible depending on what you're building or what you inherited.

Collapse
 
owl profile image
Oscar

Thanks for this nuanced response.

Agreed that there are some things that are hard to build, especially with not well-maintained codebases. But in my experiences most pages are text in boxes.

And I think testing in a variety of browsers (and assistive technology for that matter) is part of our job. Browser access can be solved by a tool like Cross Browser Test. At least for rendering and basic functionality. For advanced profiling you obviously need to have a physical device.

Hope you have a nice weekend!
Oscar