Help to get Picture and Srcset fully implemented in Microsoft Edge


  1. If you use Picturefill on any of your websites, update it to v2.3.1.

  2. Upvote the proposals for extended scrset features and the Picture element to be prioristied for implementation in Microsoft Edge.

This morning I was reading about how srcset is coming to Microsoft Edge in Windows 10 – Hooray!

But before we all celebrate too wildly, it’s worth noting that it’s not yet the full implementation of srcset. Microsoft are doing a great job of moving towards fully native Responsive Image support but this is simply the first step.

What can I do to help?

I’m glad you asked. There are two, very simple, things that you can do to help us all get full support for native responsive images sooner.

1. Update Picturefill to v2.3.1

As you may have recently read, for Edge and Webkit to fully implement srcset – in particular the currentSrc attribute – the use of Picturefill pre v2.3.1 needs to drop.

Currenty if Microsoft and Apple were to ship the currentSrc implementation in Edge and Safari, a whole bunch of websites would simply break due to a small but important bug in old versions of Picturefill.

The sooner we update any old versions of Picturefill that are used on websites that we have developed, the sooner they can implement currentSrc into Edge and Webkit.

2. Upvote the proposals for picture element support and full srcset implementation in Microsoft Edge.

Microsoft uses this to gauge and rank new features to implement in Edge and so the more upvotes they receive, the higher a priority both of these features will become.

The sooner we have native Responsive Image support across all browsers for both the Picture element and the extended srcset feature-set, the closer we will be to not having to rely on polyfills for these features in the future.

Obviously, we’ll also need to kick Apple in the nuts to get native support for picture into Webkit as well, but hopefully getting this implemented fully in Edge will help push them into action on this front.

Do your bit

Responsive Images have come a long way, but there’s still a little way to go before we have native implementation across the board.

By acting on the two simple steps above, you’ll be helping developers everywhere get a step closer to that goal.