You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(This Layout Shift is more notable when the map is larger, and on slower connections.)
We should give the element a (default) intrinsic size (300x150) before it is upgraded (:not(:defined)). These styles should only apply when Custom Elements is supported and JavaScript enabled such that we don't impose the styles on the map element in the graceful degradation/noscript scenario, in which case it may act as a container for any potential fallback content. And we also want to avoid overriding any author-provided CSS width and height declarations - shiny new contain-intrinsic-size to the rescue?
layout-shift.mp4
(This Layout Shift is more notable when the map is larger, and on slower connections.)
We should give the element a (default) intrinsic size (300x150) before it is upgraded (
:not(:defined)
). These styles should only apply when Custom Elements is supported and JavaScript enabled such that we don't impose the styles on the map element in the graceful degradation/noscript scenario, in which case it may act as a container for any potential fallback content. And we also want to avoid overriding any author-provided CSSwidth
andheight
declarations - shiny newcontain-intrinsic-size
to the rescue?Who said styling custom elements is easy? 😋
The text was updated successfully, but these errors were encountered: