Jason Lee

Right now unknown component props are forwarded to the internal `` tag, so: ```html ``` will be rendered similar to your attached code - but not for `media` attribute though....

> I'm leaning towards remove decoding to save the bytes. What do you think? I kind of disagree. IMO we do in fact by intention want *all* images to be...

The reason why `loading` and `decoding` are added is because they change `` tag defaults - IMO unless we're changing `fetchpriority` defaults there isn't a strong case to define it...

I meant the HTMLElement `` tag [default values](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#attributes); specifically `loading` and `decoding` for which we are overriding the default value. Hence: https://github.com/zerodevx/svelte-img/blob/8254cd1994b3ff20b30b72392c6f40a55ab360ad/src/lib/SvelteImg.svelte#L5-L18 These explicitly declared props are not arbitrary -...

Seems like there's activity in the related `imagetools` PR, so let's wait for that to land first.

> mention all the different toggles ... at the very least in the docs That could be *a lot* of props. 😅 But I think we could mention the salient...

Just thinking out loud - are animated images supposed to work with LQIP? If yes, how does it look like?

definitely need more info than that - could you paste your full code - or better still do a repro in jsbin.

Apologies for the late reply. There is a [somewhat related issue](https://github.com/webcomponents/webcomponentsjs/issues/1056) that should land before this I think. It might not be a good idea to transpile native module to...

How do you expect help when you give no details? Create a minimum repro in https://plnkr.co/ where we can see what's wrong.