The proposed `intrinsicsize` HTML attribute makes such a big UX difference. No more user-visible reflows as images/videos load!
I just added it to all <img>s on the @v8js website using a simple script: https://github.com/v8/v8.dev/pull/144 …https://twitter.com/css/status/1085277957873115141 …
-
-
*nudges
@ojanvafai* It would be great to address this question directly in the proposal's explainer:https://github.com/ojanvafai/intrinsicsize-attribute … -
if possible, also this one: how to combine both approaches (if that makes any sense)https://twitter.com/WebReflection/status/1093853634188754944 …
End of conversation
New conversation -
-
-
OK, but in that case it's kinda comparing apples to oranges. What I mean is: what is the difference, if not less compatibility, with this approach based on same CSS (+ height:auto) and width and height instead of that attribute?https://codepen.io/WebReflection/pen/pGpMYB?editors=0100 …
-
Although I guess the main difference is this one: > With this attribute media elements will maintain their aspect ratios In that case, would mixing the two technique work, with intrinsicsize being more important than width and height, or we have a backward compatibility issue?
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.