Inkscape fails to render webp in <image> elements

<!--See our full bug reporting guidelines at https://inkscape.org/contribute/report-bugs/ Writing a good bug report will ensure we'll be able to help efficiently. 🙂--> #### Summary: <!--Summarize the issue/suggestion concisely:--> Some SVGs, like the attached, refer to webp images in an \<image\> element. These render correctly in Chrome and Firefox, but show a broken image in Inkscape. #### Steps to reproduce: <!--Describe what you did (step-by-step) so we can reproduce:--> Open the attached SVG in inkscape, observe that the webp images are replaced with broken image icons. {width=300 height=169} #### What should have happened? {width=304 height=171} #### Related issues * https://gitlab.com/inkscape/inkscape/-/work_items/5089 shows that adding a webp to an SVG fails, which is only subtly different than this issue of displaying existing SVGs containing webps. * https://gitlab.com/inkscape/inbox/-/work_items/8887 similarly relates to embedding a base64-encoded webps. #### Version info <!--Open 'Help > About' and click on the little bug icon in the bottom right corner that copies the debug information to your clipboard. For command line users, run 'inkscape --debug-info'. For Inkscape 1.0.2 and older, please manually add the Inkscape Version and Operating System Version. The Inkscape version is listed in the About dialog. For command line users, run 'inkscape -V' Paste the information in the empty space between the apostrophes below:--> ``` Inkscape 1.4.4 (dcaf3e7, 2026-05-05) Compile (Run) GLib version: 2.86.3 GTK version: 3.24.51 (3.24.51) glibmm version: 2.66.8 gtkmm version: 3.24.10 libxml2 version: 2.15.1 libxslt version: 1.1.45 Cairo version: 1.18.4 (1.18.4) Pango version: 1.56.4 (1.56.4) HarfBuzz version: 12.2.0 (12.2.0) OS version: Windows 11 22H2 ``` <!--❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️ Please be patient while we try to find the time to look into your issue. Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports.--> <!--Please be careful when/after writing # for example in logs, code, or versions of linux - use inline code span - single backticks (`) before and after it, like this - `inbox#1618` - use multi-line code block - triple backticks (```) to fence/enclose console logs - attach long logs as a text file.-->

issue