Issue metadata
Sign in to add a comment
|
canvas tainted by video served via redirect even if both domains have CORS header set to *
Reported by
g...@imagingthing.com,
Dec 3
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 Steps to reproduce the problem: 1. open chrome browser 2. open dev console 3. run the attached html file in open browser 4. view response in console. 5. or, follow this link to run the above on a server https://viddang.imagingthing.com What is the expected behavior? video loads, creates a poster image, console logs "got it" What went wrong? chrome 70 canvas tainted on videos served from a different domain via a redirect, even if initial domain and serving domain both have CORS set to * (or to originating domain). no problem with video served from same domain. Did this work before? Yes 69.0.3497.92 Does this work in other browsers? Yes Chrome version: 70.0.3538.110 Channel: stable OS Version: 6.2 (Windows 8) Flash Version: works in Firefox 63.0.3(64 bit)
,
Dec 4
Able to reproduce this issue on Windows 10, Mac OS 10.13.6 and Ubuntu 17.10 on the latest Stable 70.0.3538.110. Issue seems to be fixed on the latest Canary 73.0.3629.0 and Beta 71.0.3578.75. Reverse Bisect Information: ============================ Good Build: 72.0.3606.0 Bad Build : 72.0.3605.0 By running the per-revision bisect script, below is the Changelog URL. https://chromium.googlesource.com/chromium/src/+log/a684019a8f7a92b7ea98445c96b5615a741f7b1f..657a055a66492e996b296d7bb999e3c8551eed23 From the above Changelog, suspecting the below Change. Reviewed-on: https://chromium-review.googlesource.com/c/1325281 yhirano@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner. Thanks...
,
Dec 4
gary@, can you try with Chrome 71 (i.e., current beta)?
,
Dec 4
,
Dec 4
Hi, we have the same issue with the CORS headers and HTTP redirects. And Chrome 71 is working correctly again. So Chrome 70 has this bug which is fixed in Chrome 71. So I can confirm that this is working for us again with Chrome 71.
,
Dec 4
Yes, it's working in 71. Thank you so much.
,
Dec 5
Thank you. I broke the functionality at 70, fixed it at 72 and merged the fix to 71. I didn't merge the fix to 70 because merging to stable is somewhat risky. Sorry for the inconvenience, but please wait for Chrome 71. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Dec 4