Recently the W3C Technical Architecture Group published a new finding on the role of polyfills on the web. I was the primary author of the finding and in this talk I present the findings recommendations for a developer audience.
web app for the FT (app.ft.com) 2. Created our Origami component system 3. Ran FT Labs for 3 years 4. Now working with Nikkei to rebuild nikkei.com 5. W3C Technical Architecture Group 6. Polyfill.io 7. A bit obsessed with mascots 7
such as: • Comprehensive test suite, especially if it includes relevant Web Platform Tests • Effects on the performance profile of your site, measured using in-browser profiling tools or other auditing or monitoring tools or services 21 https://github.com/w3c/web-platform-tests
user's time, money and data allowance • Feature detect + conditional loading can delay the loading of necessary polyfills • But better to optimize for modern browsers anyway • If the worst-case set of polyfills is small, maybe serve them anyway 22 https://html5test.com
a risk to evolution of the web • Fine for private content / apps ◦ programme guide on TV ◦ in-flight entertainment UI on aircraft seat • NOT OK if the device can browse the public internet • For polyfilling: "least capable" category includes these 39