-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
"The canvas has been tainted by cross-origin data" caused by img attribute order on some browsers #196
Comments
this also work within order of codes
|
What if i'm using it on an image url?
Where would the |
this is not working |
In my case, the canvas stops displaying the image if I add |
I solved the issue by using a dummy GET parameter in the src. |
SAME HERE. I tried the fix w/ the dummy parameter and it also didn't work. |
i tryed all ways. It doesn't work for me |
Same here |
for me, I have 2 issues relative to cors+canvas :
|
If the image doesnt appears, you need to enter into the web using a local host connection. I use to try with XAMMP APACHE. |
Have encountered the same issue when trying to get color of the image located in my Roku TV with this URL http://192.168.1.11:8060/query/icon/12. |
The crossOrigin attribute allows images that are loaded from external origins to be used in canvas like the one they were being loaded from the current origin. Using images without CORS approval taints the canvas. Once a canvas has been tainted, you can no longer pull data back out of the canvas. By loading the canvas from cross origin domain, you are tainting the canvas.
You can prevent this by setting
crossorigin="anonymous"
.However, CRAZILY enough, the order of the attribute on the
img
element does matter. I've been writing HTML since 2005 and this is the first time I found something like this. Thecrossorigin
attribute must come before thesrc
. On Chrome the order did not matter, but on Safari (and other mobile browsers) it solved the problem.<img src="...image.jpg" crossorigin="anonymous" />
will result in
Unhandled Rejection (SecurityError): The operation is insecure.
while
<img crossorigin="anonymous" src="...image.jpg" />
works just fine.
Writing this down here so it can be added to the documentation and hopefully help someone in the future.
The text was updated successfully, but these errors were encountered: