Kagi Translate mishandles images with an srcset

acut3

When translating a website, Kagi Translate URL-encodes any space that appears in the srcset of an image. This is not correct, since srcset uses spaces between image candidates, and between an image candidate and its condition descriptor. These spaces need to be preserved.

The result is that any image that uses an srcset will fail to load in Kagi Translate.

For example, try to load https://habr.com/ru/companies/timeweb/articles/776040/ in Kagi Translate. All images will be missing. Now look at the first image in the original site. It's defined with:

<img src="https://habrastorage.org/r/w1560/webt/2h/l_/2y/2hl_2ykodvjs5zkodjmxix4ehke.jpeg" sizes="(max-width: 780px) 100vw, 50vw" srcset="https://habrastorage.org/r/w780/webt/2h/l_/2y/2hl_2ykodvjs5zkodjmxix4ehke.jpeg 780w,
       https://habrastorage.org/r/w1560/webt/2h/l_/2y/2hl_2ykodvjs5zkodjmxix4ehke.jpeg 781w" loading="lazy" decode="async">

But Kagi Translate has transformed it into:

<img src="https://habrastorage-org-adblock.kagiproxy.com/r/w1560/webt/2h/l_/2y/2hl_2ykodvjs5zkodjmxix4ehke.jpeg" sizes="(max-width: 780px) 100vw, 50vw" srcset="https://habrastorage-org-adblock.kagiproxy.com/r/w780/webt/2h/l_/2y/2hl_2ykodvjs5zkodjmxix4ehke.jpeg%20780w,&amp;" loading="lazy" decode="async">

So the browser will try to load https://habrastorage-org-adblock.kagiproxy.com/r/w780/webt/2h/l_/2y/2hl_2ykodvjs5zkodjmxix4ehke.jpeg%20780w,&, which of course doesn't exist.

Kagi Translate should not URL-encode spaces in the srcset attribute of images.

acut3

Any news on this?

I got pretty verbose in my description, but the net effect is that all images are missing from the translated page.

Another example, the website of the largest newspaper in France: https://translate.kagi.com/www.lemonde.fr

acut3

BTW, the same problem also exists when srcset is used in the <source> element of a <picture> element. An example of this is https://translate.kagi.com/www.spiegel.de, where all images are missing after translation.

acut3

[edited]
So, I thought it was fixed, but it's only because when the Kagi Translate extension is installed, the "translate site" feature now falls back to using the extension (so, it doesn't use kagiproxy). When the extension is not installed, kagiproxy is still used and srcset is still broken.