That means, Podlove Publisher sends https://example.com/wp-content/uploads/2022/12/123-350x350.jpg to Auphonic which is much smaller than the original size image which would be https://example.com/wp-content/uploads/2022/12/123.jpg and is contained in the srcset attribute.
Expected behavior
Podlove Publisher uses the widest image available from srcset or falls back to src.
I'm happy to propose a fix for this but wanted to open an issue for feedback/context either way.
My suggestion would be to iterate through srcset and find the largest image and optionally fall back to src.
This is an issue I discovered this week with a change I added in https://github.com/podlove/podlove-publisher/pull/1241
In this code
https://github.com/podlove/podlove-publisher/blob/52e146f0317e26df698b11659eca243288d7582e/lib/modules/auphonic/admin.js#L274-L275
the element selected by
$('#set-post-thumbnail > img').attr('src')
looks something like this:That means, Podlove Publisher sends
https://example.com/wp-content/uploads/2022/12/123-350x350.jpg
to Auphonic which is much smaller than the original size image which would behttps://example.com/wp-content/uploads/2022/12/123.jpg
and is contained in thesrcset
attribute.Expected behavior
Podlove Publisher uses the widest image available from
srcset
or falls back tosrc
.Actual behavior
Podlove Publisher always uses
src