5 ms·
Web Developers shouldn't need to "support" particular browsers at all, that's what standards are for. Nobody should be "supporting" any non-standard functionali
by jessehattabaugh 3y ago
Web Developers shouldn't need to "support" particular browsers at all, that's what standards are for. Nobody should be "supporting" any non-standard functionality at all.
- azangru 3y ago> Web Developers shouldn't need to "support" particular browsers at all, that's what standards are for. I agree. But different standards get adopted by different browsers at different rates. Case in point: Firefox still has not released support for declarative shadow DOM. As a side note, although related to standards: I thought Firefox insisted several years ago that they were not going to support File System Access API. But now MDN lists it among supporting browsers.
- godshatter 3y agoIn this case, though, a government website should be aiming to support the lowest common denominator in web standards. They shouldn't be writing websites that require something like the shadow DOM or the File System Access API. Standards low enough that actually testing against different browsers is an afterthought.