10 Reasons To Stop Supporting Internet Explorer

Subresource Integrity

Let’s say you were loading a JavaScript file from a third-party server. What if that server was compromised by Hacker Cat and then he added cryptomining code to the external JavaScript file? It was modified to secretly mine DOGECOIN.

Hacker Cat is especially crafty, knowing to strike when the system admins are asleep or on a long vacation. How would you know something went wrong? How long would this go on undetected? More importantly, how would you prevent it?

The easiest third-party code to secure is no third-party code. But if a CDN simply must be used, you can verify that code with a cryptographic hash.

See the Mozilla Developer Network for additional information, but the short version is this — you generate a hash of the file that you determine to be safe and then you add that hash to your HTML code using the “integrity” attribute. So, if the JavaScript file was altered, either in transit or on the third-party server, the web browser is supposed to reject that file.

But if the web browser is Internet Explorer, that check doesn’t occur. It doesn’t support the Subresource Integrity feature. If you need to argue why support for Internet Explorer support should be dropped, that’s a pretty strong reason.


Input Type “Date”

Security is an important part of building a website, and it is related to the eight feature on this list. If your visitors can enter data, that data needs to be sanitized. Typically, there are two sides to sanitization. The first side is client side. Before the data is sent to the server, the user is alerted to possible errors — such as entering February 31st. That date is not valid.

That’s why this input type is really nice. With the pop-up calendar grid, it automatically enters in an appropriate value — including the full year. The user only needs to click or tap a date.

This input field is not connected to anything. It’s just so you can see how the new calendar popup works. This is only part of the picture, as it’s just client-side. If this value is being sent to a server, then additional checking would be necessary on the server-side. Also, this feature is still a little new, as Safari and Firefox could use some more work.

But overall, I certainly see potential here. With the “Reminders” widget, there isn’t the option to set a date on new reminders. But now that I know about this new feature, it might not be so difficult to improve the widget.


Animated Portable Network Graphics (APNG)

There are other improvements available if you’re not supporting Internet Explorer, the ninth item on this list is another example. The ability to use Animated Portable Network Graphics is an upgrade — if for no other reason than we can stop having to debate on how to pronounce GIF.

Although, I’m not sure if APNG is the correct pronunciation for this new format. I assume the acronym is just spelled out.

Anyway, the GIF image format is surpassed by APNG. While the former was a pillar of the early Internet, the latter can display 24-BIT images and with 8-BIT transparency. Also, the file size for an APNG can be smaller than a GIF.