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
{{ message }}
This repository was archived by the owner on Aug 19, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 19, 2022. It is now read-only.
I'm seeing this too, if I run the code in a React app the image is loaded twice, however if I grab the output html and run it in a static html file the problem does not occur.
One of the call is made by dist.js which is this library and another one is made by react-dom.development.js which I think is called only in dev mode or when network cache is disabled in chrome dev tools as mentioned by @Loque-
I thought it was, but it's only if you have the cache disabled in devtools that this behaviour exists.
From what I can tell it's not an issue. Without a test case to demonstrate it, the GitHub issue should probably be closed to prevent people thinking it is still a problem.
Activity
[-]Delay prop loads the image twice[/-][+]Image is loaded twice[/+]hilja commentedon Aug 4, 2019
Was wondering the same just.
7oque commentedon Dec 2, 2019
I thought it was, but it's only if you have the cache disabled in devtools that this behaviour exists.
morganfeeney commentedon Dec 13, 2019
I'm seeing this too, if I run the code in a React app the image is loaded twice, however if I grab the output html and run it in a static html file the problem does not occur.
sanishkr commentedon Dec 24, 2019
One of the call is made by
dist.jswhich is this library and another one is made byreact-dom.development.jswhich I think is called only in dev mode or when network cache is disabled in chrome dev tools as mentioned by @Loque-mattg66 commentedon May 30, 2020
Hi, I am also having this issue. Cache is not disabled in dev tools, and image is being loaded by both dist.js and react-dom.production.min.js
endrureza commentedon Jul 31, 2020
has this issue been solved?
7oque commentedon Jul 31, 2020
From what I can tell it's not an issue. Without a test case to demonstrate it, the GitHub issue should probably be closed to prevent people thinking it is still a problem.
adshrc commentedon Nov 23, 2020
For me it was just the case while dev tools cache was disabled. Thanks!