Hi,
I'm using the RenderToImage functionality. There seems to be a baked in <img> element cache based around the "src" attribute. This means that if the url has an issue (e.g. cdn failure) on the first time RenderTomImage processes an image, all that will remain is an ugly broken image. Appending a parameter ("test.img?v=123281") does trigger a new download, but going back to the original url ("test.img") still refers to the broken image reference.
I'm wondering if there is a way to have the RenderToImage functionality force a refresh of the image cache ("test.img") without appending values inside the html itself (e.g. "test.img?v=2").
Comments: Hey, I believe my commit today fixed the issue. You can get the latest code from [GitHub](https://github.com/ArthurHub/HTML-Renderer), will do a proper release soon. Note that v1.5 has some library changes you will have to adjust your code to. Let me know if it worked.
I'm using the RenderToImage functionality. There seems to be a baked in <img> element cache based around the "src" attribute. This means that if the url has an issue (e.g. cdn failure) on the first time RenderTomImage processes an image, all that will remain is an ugly broken image. Appending a parameter ("test.img?v=123281") does trigger a new download, but going back to the original url ("test.img") still refers to the broken image reference.
I'm wondering if there is a way to have the RenderToImage functionality force a refresh of the image cache ("test.img") without appending values inside the html itself (e.g. "test.img?v=2").
Comments: Hey, I believe my commit today fixed the issue. You can get the latest code from [GitHub](https://github.com/ArthurHub/HTML-Renderer), will do a proper release soon. Note that v1.5 has some library changes you will have to adjust your code to. Let me know if it worked.