Hate the complexity of modern front‑end web development? I send out a short email each weekday on how to build a simpler, more resilient web. We need to plan for failure with everything we build, because it’s inevitable. NOTE: Due to some spam on the forums, posting links is currently restricted, so I had to substitute the dots in the link with (dot) in order for the forum to allow me to post it. Most importantly, I’ll still use progressive enhancement with a server fallback when I can, because things break in browsers all the time. Mozilla also has a service called Searchfox that allows you to search through specific parts of the Firefox source code. For core-features that are essential to how an app works, I use a combination of older and better supported browser methods, polyfills, and transpiling to get broad support.
They get hard jumps to anchor links instead. That’s a progressive enhancement that doesn’t work in IE or Opera Mini. An example of this might be smooth-scrolling to anchor links. For nice-to-have features and extras/flourishes, the feature only works in modern browsers.This means different things for me depending on context. This is where, in my opinion, the nuance really comes in. It also excludes popular but feature-lite browsers like Opera Mini. It does not include legacy browsers like IE (including IE 11). It also includes the most popular and common mobile browsers: WebKit View, Chrome, and FireFox on Android Safari on iOS. But what does that mean, actually?įor me, a modern browser is one of the evergreen (automatically updating) desktop browsers: Edge, Firefox, Chrome, and Safari. I often say that “I support all modern browsers” with the code that I write. The nuance of browser support with JavaScript
0 kommentar(er)
