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 has been archived by the owner on Aug 1, 2022. It is now read-only.
I'm testing the following code on two devices at the same time (mobile and desktop). Both using firefox. Did not try with chrome.
imgSrc is either a jpeg in the same folder or a base64 string.
I got a server that shows the following component on all clients at the same time for ~30seconds.
After that delay, i'm not displaying it anymore. so the react event componentWillUnmount() is fired and log me in the console the canvas. I can see that the image property of the component is always filled (either if i used the local jpeg or the base64 string).
Sometimes, randomly, really randomly, the canvas hasn't the imgSrc displayed. It's a white background. Sometimes on both devices, sometimes on 1 of them, sometimes everything is fine.
Hello !
I'm testing the following code on two devices at the same time (mobile and desktop). Both using firefox. Did not try with chrome.
imgSrc
is either a jpeg in the same folder or a base64 string.I got a server that shows the following component on all clients at the same time for ~30seconds.
After that delay, i'm not displaying it anymore. so the react event
componentWillUnmount()
is fired and log me in the console the canvas. I can see that the image property of the component is always filled (either if i used the local jpeg or the base64 string).Sometimes, randomly, really randomly, the canvas hasn't the
imgSrc
displayed. It's a white background. Sometimes on both devices, sometimes on 1 of them, sometimes everything is fine.Did I made a mistake somewhere ?
Left and Right are two different clients
![image](https://user-images.githubusercontent.com/17033907/71620558-d24ef700-2bca-11ea-8763-1b49f97c1fac.png)
Both seems to log the same component when
componentWillUnmount()
is firedThe text was updated successfully, but these errors were encountered: