`image` crate `default` feature is not set by `iced_graphics` which causes image rendering to fail silently when using custom runtime

[tomben13]

Is your issue REALLY a bug?

• My issue is indeed a bug!
• I am not crazy! I will not fill out this form just to ask a question or request a feature. Pinky promise.

Is there an existing issue for this?

• I have searched the existing issues.

Is this issue related to iced?

• My hardware is compatible and my graphics drivers are up-to-date.

What happened?

When using a custom runtime like examples/integration is doing, images added to the view don't render. The reason is that in this particular setup, with the image feature set for iced_widget, iced_renderer, iced_wgpu and iced_graphics, the default feature of the image crate is not set. This is not the case when directly using the iced dependency which itself sets the default feature.

What is the expected behavior?

Images should render.

iced_graphics should set the default feature of the image crate.

Version

crates.io release

Operating System

Linux

Do you have any log output?

[tomben13]

If a maintainer is OK with my explanation, I can file a PR to change graphics/Cargo.toml and add "image/default" to the image feature.

[pml68]

I don't think it should necessarily set said feature, since iced also doesn't set it when using the no-codec image feature flag.

[tomben13]

So maybe we should add the image-without-codecs to the other crates then