Add "loading" attribute for img/iframe HTML elements#5442
Conversation
I don't think we need to roll this back, but just as a future reference, I think we should not be so quick to close unresponsive PRs during December and early January. Many of my European clients have been off work since the 20th (or earlier) and won't return until Monday, January 6 (or later). I would not be surprised if the author of the original PR never saw your requests for follow up. |
|
Ah, gotcha! I thought it would be reasonable to get a new PR since it’s been close to a month of no response, though I guess I got a bit overzealous. 😛 |
* Update img.json with `loading` attr * Update iframe.json with `loading` attr * Update iframe.json * Fix linter errors Co-authored-by: Robert Linder <[email protected]>
|
I discovered while reviewing #7591 that the data added here is off by one milestone. It trusted https://chromestatus.com/feature/5645767347798016 which said 76, but https://storage.googleapis.com/chromium-find-releases-static/0fc.html#0fc50ca2d3c81f74f73aae8aab6079a516d9b8fb and https://bugs.chromium.org/p/chromium/issues/detail?id=709494 show it's actually 77. I've updated the chromstatus.com entry. @vinyldarkscratch can you update the data for |
Supersedes #5284 due to lack of response from the author. This PR adds the
loadingattribute to the<img>and <iframe>` elements, and fixes the linter errors within the original PR.Enabled by default in Chrome 76: https://chromestatus.com/feature/5645767347798016
Bugzilla bug: https://bugzil.la/1542784 (seemingly only for
<img>, thus only added toimg.json)Webkit bug: https://webkit.org/b/196698