You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When people try to download different post (an HTML ref), they should see different images downloaded
Current Behavior
When people try to download different post (an HTML ref), though different images are rendered on browser properly, they should see the same image downloaded (always the image from the first post they try to download)
This is what they see when downloaded
Possible Solution
I dont know, is this cashing issue?
Steps To Reproduce
...
...
...
Error Message & Stack Trace
<!-- Provide a log message if relevant -->
Additional Context
Users of my product cannot use it properly
Let users download different elements on the webpage
You can try by going to drlambda.ai, and sign up (for free), create a social post, and then download the different pages of it.
Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it.
To help make it easier for us to investigate your issue, please follow the contributing guidelines.
We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
Expected Behavior
When people try to download different post (an HTML ref), they should see different images downloaded
Current Behavior
When people try to download different post (an HTML ref), though different images are rendered on browser properly, they should see the same image downloaded (always the image from the first post they try to download)
This is what they see when downloaded
Possible Solution
I dont know, is this cashing issue?
Steps To Reproduce
Error Message & Stack Trace
Additional Context
Users of my product cannot use it properly
Let users download different elements on the webpage
You can try by going to drlambda.ai, and sign up (for free), create a social post, and then download the different pages of it.
Your Environment
node -v
v18.12.1
The text was updated successfully, but these errors were encountered: