When using an image thumbnail to scale an SVG image with the following configuration:

Note that it has enabled Force <picture> HTML tag (to make it consistent with non-SVG images).
And calling it in Twig like:
pimcore_image('image', {
removeAttributes: ['width', 'height'],
class: 'image__img text-image-left-right__image',
thumbnail: 'three_column_text_image_svg',
cacheBuster: true,
})
I'm getting an invalid output:
<picture data-alt="" data-default-src="/cache-buster-1585728835/content/CMS/Illustrationen%20USP%27s/Preis.svg">
<source srcset="/cache-buster-1585728835/content/CMS/Illustrationen%20USP%27s/Preis.svg 1x, /cache-buster-1585728835/content/CMS/Illustrationen%20USP%27s/Preis.svg 2x" type="image/webp">
<source srcset="/cache-buster-1585728835/content/CMS/Illustrationen%20USP%27s/Preis.svg 1x, /cache-buster-1585728835/content/CMS/Illustrationen%20USP%27s/Preis.svg 2x" type="image/png">
<img class="image__img text-image__image" alt="" src="/cache-buster-1585728835/content/CMS/Illustrationen%20USP%27s/Preis.svg">
</picture>
The problem here is, that:
type is invalid, an image does not have the type 矛mage/png nor image/webp.When disabling Force <picture> HTML tag I'm getting a single image without high res or low res, which is correct. But I want to have the <picture> tag to be consistent with rastered images for styling purposes.
Rendering SVG images with image thumbnails should not cause high res or low res alternatives, nor should it cause invalid types.
It does.
Maybe I'm wrong, but I also think cacheBuster: true isn't working for SVG images. I'm still getting the URL without cache-buster prefix when calling .getSrc() or .getThumbnail()
Cache buster works for me, used the following code:
{{ pimcore_asset(368).thumbnail('bernie').html({
cacheBuster: true
})|raw }}
Furthermore the type is invalid, an image does not have the type 矛mage/png nor image/webp.
<img> does not but <source> does.
@NiklasBr what @julmot actually meant is that:

馃槈
:D I thought it was a general comment: "An image does not have the type..." which of course it can have, not specific to this .svg bug