Align the HTMLImageElement's cross-origin-redirects check with the HTMLVideoElement's one
Categories
(Core :: DOM: Core & HTML, task)
Tracking
()
People
(Reporter: chunmin, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
This is a follow-up bug for bug 1774300.
The HTMLImageElement's result of having cross-origin redirects or not is different from the one obtained in HTMLVideoElement in the same situation.
If the HTMLImageElement's src is in a cross-origin domain but redirected to the same domain, then it thinks it has no cross-origin redirect. However, in the same case, the HTMLVideoElement consider the src has a cross-origin redirect.
This is found during implementing VideoFrame when I was trying to use the nsLayoutUtils::SurfaceFromElement for HTMLImageElement and HTMLVideoElement.
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Do the tests require the patch from bug 1240357? If so can we land this with the tests failing then use the tests to land the patch in bug 1240357 to fix them, or would you like me to fix up bug 1240357 without tests and give it to you to review so you can test it with this patch?
| Reporter | ||
Comment 3•3 years ago
•
|
||
It looks like bug 1240357 is for SVGImageElement, and it's irrelevant to this bug. The fix for bug 1240357 won't fix the issue in imgIRequest::hadCrossOriginRedirects (The getter is implemented here).
| Reporter | ||
Comment 4•3 years ago
|
||
Description
•