Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When I call toPng for a second time on a different ref, the image is still old #444

Closed
Qualia-Li opened this issue Dec 20, 2023 · 2 comments
Labels

Comments

@Qualia-Li
Copy link

Expected Behavior

When people try to download different post (an HTML ref), they should see different images downloaded
image

image

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
night elf (1)
night elf (2)
night elf (3)

Possible Solution

I dont know, is this cashing issue?

Steps To Reproduce

  1. ...
  2. ...
  3. ...
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.

Your Environment

node -v
v18.12.1

  • html-to-image: [e.g. 0.1.0]
  • html-to-image@1.11.11
  • OS: [e.g. macOS Sierra 10.12.3]
  • macOS ventura 13..0
  • Browser: [e.g. chrome 78.0.3904.108]
  • chrome 120.0.6099.109
@Qualia-Li Qualia-Li added the bug label Dec 20, 2023
@biiibooo
Copy link
Contributor

biiibooo bot commented Dec 20, 2023

👋 @Qualia-Li

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.

@Qualia-Li
Copy link
Author

this fixes the issue

#431

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant