Gregory's Server@downey Occasionally there's a browser feature that is required for basic functionality of a web app, but you can almost always detect if it's missing from a few lines of javascript code, and only show the warning then.
|
2 comments
LisPi
@ZahmbieND @downey That's also literally the point of polyfills. It wouldn't the that hard to generate versions for known browsers and then one that assumes you barely implement anything and polyfills nearly everything. That being said, sites should work with no arbitrary code execution (typically #Javascript) at all. |
@downey An example I've dealt with was an ASP .NET Blazor website, which requires webassembly for basic loading of the page. At the time I started the project, we had a significant number of users still on Internet Explorer, so I added a javascript file to the root page that detects if webassembly is missing and shows a popup suggesting to open Edge. That prevented me from needing to maintain a list of browsers which either do or don't support it, and I could just let the browser tell me itself.