with keeping their websites compatible across various versions. This problem exemplified as more modern browsers like Firefox and Chrome were added to the mix, forcing many web devs to create websites that could utilize modern features and fall back onto old ones for users still on IE. Today, these problems are largely solved, but not entirely. There is still some feature disparity between Edge, Chrome, Safari, and Firefox...and even now some developers need to continue to support Internet Explorer. It's also widely known that as newer versions of these browsers seem to squash more of these differences, users won't always have the most up-to-date version of the browser due to update neglect, or system compatibility. In this episode, Matt and Mike focus on CSS feature disparity between browsers and how to handle site development when your user base doesn't all have the latest features that you're utilizing. When is it safe to use a new CSS feature on a production website?

Show Notes: https://www.htmlallthethings.com/podcasts/css-browser-support-when-can-i-use-this

Scrimba Discount: https://tinyurl.com/ScrimbaHATT

1b:T54e,

Back in the days of Internet Explorer web developers struggled with keeping their websites compatible across various versions. This problem exemplified as more modern browsers like Firefox and Chrome were added to the mix, forcing many web devs to create websites that could utilize modern features and fall back onto old ones for users still on IE. Today, these problems are largely solved, but not entirely. There is still some feature disparity between Edge, Chrome, Safari, and Firefox...and even now some developers need to continue to support Internet Explorer. It's also widely known that as newer versions of these browsers seem to squash more of these differences, users won't always have the most up-to-date version of the browser due