mlc-ai / mlc-ai/web-stable-diffusion
Image Save/Copy Issue - Grabs Previous Image Instead of Current One
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 3.7k
- Forks
- 238
- PR merge metrics
- No merged PRs in 30d
Description
When trying to copy or save an image on the demo webpage, it always takes the previous image instead of the currently displayed one. Additionally, if you attempt to copy or save the first generated image, it results in a transparent 512x512 image instead.
Steps to reproduce:
- Generate an image.
- Attempt to copy or save the first generated image.
- Generate another image.
- Attempt to copy or save the second image.
Expected results:
- The first image should be copied/saved as a proper image.
- The second image should be copied/saved.
Actual results:
- The first image results in a transparent 512x512 image when copied/saved.
- The first image is copied/saved instead of the second image.
Environment:
- Operating System: Windows 11
- Browser: Chrome Canary Version 114.0.5715.0 (Official Build) canary (64-bit), launched with --enable-dawn-features=disable_robustness
- GPU: Radeon RX 7900 XTX
Please investigate this issue, as it prevents users from properly saving or copying the most recent image.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the demo webpage's image generation flow and the code handling copy and save actions. Reproduce the issue by generating two images, then compare which image each action uses. Done means the first generated image is copied or saved correctly and subsequent actions use the currently displayed image rather than the previous one.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100