sueoutlet
Forum Replies Created
-
You are most welcome, Loukky. 🙂
Hello There,
Yes, I previously confirmed that the characters are removed in the src attribute when the Lazy load processes the image. Only that I wasn’t able to reproduce the image returning 404 error.
However, I checked this again from another browser (like Safari) and I confirm that, while Chrome may still manage to request the encoded version, so the images load, this is not always the case, for example, with Safari, it takes the stripped URL, causing the broken image.
I’ve opened a GitHub issue about this so the dev team can further investigate.
You can also subscribe to it so you get updates on the progress
Regards
Hello there,
Thank you for reaching out to us.
I was able to reproduce the issue you’ve pointed out on my end, with the character being removed from thesrc.
This is an intended behaviour to avoid vulnerability issues with the Lazyload feature, to make sure that the src attribute is matched with only safe values.Per my test, the image will still be encoded correctly, and it should not result in any broken images.
If you’ve noticed any broken images, we’d appreciate it if you could share more details on how to reproduce it.
Thank you
