> Review raised, completed and closed within 24 hours. This is a TAG record. 👏 👍 > If a client requests an HTML page, and the page has a link preload header for a logo image, but the server has two variants of that logo, PNG and WEBP, which do we push, given that the Accept header on the HTML request is not providing information about the client's preferred image formats. That's not true, and we learned this the hard way a few times over now. Browsers that support WebP should (and do) advertise webp on all requests; same best practice applies to all other formats. > We're nervous of developer confusion between prefetch and preload. What efforts are being made to explain the difference between the two, and is it time to deprecate prefetch officially? No it's not, but we can probably make prefetch better and smarter. In terms of differences, preload and prefetch serve different purposes. Addy and Yoav have good explainers here: - https://medium.com/reloading/preload-prefetch-and-priorities-in-chrome-776165961bbf#89a4 - https://www.smashingmagazine.com/2016/02/preload-what-is-it-good-for/#didnt-we-already-have-that Open to suggestions on how to explain prefetch better, let's route that feedback into Resource Hints spec. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/202#issuecomment-332593484
Received on Wednesday, 27 September 2017 17:21:13 UTC