Contact [email protected] Explainerhttps://github.com/whatwg/html/issues/4654
Specificationhttps://html.spec.whatwg.org/#sizes-attributes Summary Auto Sizes allows developers to set the sizes attribute to auto (sizes=auto) for lazy loaded image elements with srcset. For this use case the image's width and height should be provided. The browser will use the layout width of the image in order to select the source url from the srcset. Blink componentBlink>Image <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EImage> Search tagssizes <https://chromestatus.com/features#tags:sizes>, sizes=auto <https://chromestatus.com/features#tags:sizes=auto>, autosizes <https://chromestatus.com/features#tags:autosizes>, srcset <https://chromestatus.com/features#tags:srcset> TAG review TAG review statusNot applicable Risks Interoperability and Compatibility None since all major browsers (Chrome, Safari and Firefox) indicate that they would be willing to implement it. *Gecko*: Positive (https://github.com/mozilla/standards-positions/issues/650 ) *WebKit*: Positive (https://github.com/WebKit/standards-positions/issues/9) *Web developers*: No signals *Other signals*: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? Debuggability Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?Yes Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?Yes PR for current tests pending merge: https://github.com/web-platform-tests/wpt/pull/34427 Rendering wpt.fyi tests will be included with the prototype CL. Flag name on chrome://flagsAutoSizeLazyLoadedImages Finch feature nameNone Non-finch justificationNone Requires code in //chrome?False Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1359051 Estimated milestones DevTrial on desktop 122 DevTrial on Android 122 Anticipated spec changes Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way). Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5191555708616704 Links to previous Intent discussionsIntent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/AYoqvNluyeA This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFxahvuCb7xXip6nqDAykaRGXy5uX3%2BXZsuPY62s9ntV03PDqw%40mail.gmail.com.
