DEV Community

Daniel Cuttridge
Daniel Cuttridge

Posted on

Why Include Browser Updates As Part Of Your Dev Cycle?

Browser updates and the development cycles of new versions of browsers seem to be increasing…

Chrome release history:
2019– 11 releases
2018– 8 releases
2017– 8 releases
2016– 8 releases

Disclaimer: I’m focusing on Chrome here and not Firefox as Chrome has around 70% market share for desktop users. Though all of my points hold equally valid with Mozilla Firefox as well.

In 2019 we saw some pretty big changes, and most of the big ones pertain to good things such as improved load times, security and privacy.

In order to achieve this, browsers are having to scrutinize websites more closely than ever.

This is changing the landscape online, and it’s costing brands, small businesses, and startups money...

Starting in Chrome 79 Google announced that they would start blocking what is called Mixed Content…

Mixed content would be any resource that loads with http:// on a https:// website.

This is a security measure, and any content that is “mixed” will contain insecure content.

Thankfully a lot of people are going to get away with it, as they are placing in provisions that will auto-upgrade content such as images to https:// by the time Chrome 81 released in February 2020.

Note: It can only do this if your site has an https:// version available, they aren’t accessing your site and changing it. Rather they are changing the file in the browser and then providing the alternative. This comes with an obvious speed or load time cost.

Additionally, this is important for SEO...

In 2019 Google rolled out an Evergreen version of Chromium for site rendering. This means that Google can finally see your website the same way as you do (for the most part).

As browsers continue to change what they will and won't display, the benefit to staying up to date with them is clear.

Stay up to date with the changes:

Top comments (0)