Alex RussellNo, but seriously...why don't we have `<video loading="lazy">` yet?
Matt Campbell@slightlyoff I wonder if it's relevant here that Google would naturally prefer that all the world's (public) videos be on YouTube, which likely has a JavaScript-based lazy loading implementation for embedded videos.
BasiqueEvangelist@matt Honestly if that was the case then they should've at least optimized the YouTube iframe widget. 1.2MB for a video embed?
(Source is https://www.zachleat.com/web/youtube-embeds/)
Curtis Wilcox@slightlyoff
`preload=metadata` sounds like a sufficient default. I guess not all browsers use it.
Maybe add a lazy option for `poster`?
Sasha Firsov@slightlyoff , because there is a lazy load for JS and most of things is done by JS.
Extending the HTML with Declarative Custome Elements should do the trick even with JS disabled.
Otherwise w3c HTML expansion would grow forever
niu tech@Suns @slightlyoff It's Declarative Shadow DOM: https://developer.chrome.com/docs/css-ui/declarative-shadow-dom
@niutech, template and shadow is not an answer for mylti-vendor code, <custom-element> is :p
@niutech ,
Declarative Shadow DOM from https://web.dev/articles/declarative-shadow-dom
has nothing to do with Declarative syntax. It is still relying on JS to function. DCE would be the no-js answer.
@niutech , π htmlz, the base for #PHOOOS . Interesting concept. Still needs some polishing towards pure DCE.
Till this moment I thought only
<custom-element> covers no-js patterns of #DeclarativeCustomElement
@slightlyoff We have <πππππ πππππππ="ππππ"> and <ππππππ ππππππ="<πππππ πππ='...' π ππππ='π·πΆπΆ%'></πππππ>" πππππππ="πππ£π’"></ππππππ> without using #JS.