Martin Janecke

Maybe I misunderstand, but don't all of these opt-in suggestions require JavaScript, which would be contrary to "[compelling use cases such enabling scoped styles without requiring Javascript](https://github.com/whatwg/dom/issues/831)"?

Apparently there used to be a `lowsrc` attribute for ``, but it’s listed as non-conforming with the following hint: > Use a progressive JPEG image (given in the src attribute),...

Please support encoding progressive JXLs so that the content of an image can be displayed (in a lower quality) already before the file is fully downloaded on the web. This...

Could it be implemented for same-origin iframes please even if not all security concerns are sorted out for the foreign-origin scenario yet?

Just a note on why this would be useful, even if only for same-origin iframes in the beginning: With Edge soon using chromium, all major browsers will support ``, and...

@othermaciej > Many sites have password restrictions, including ones that are popular and actively maintained. The actively maintained sites could be educated to lessen their technical restrictions. They could still...

> Thank you for proposing JPEG XL image format for inclusion in Interop 2025. > > We wanted to let you know that this proposal was not selected to be...

> Yeah, I'm def down with the concept. Question is just if we think there's a necessity for full art-direction (multiple `source` elements) or if it's fine to _just_ provide...

I assume bots would be made that specifically gather content that is marked as sensitive so that it can be more efficiently exploited. As for telling AI not to consume...

> The argument that sites may misuse this API is, I think, the same argument for any powerful API: notifications, fullscreen, storage, autoplaying audio, even things we don't mediate well...