All videos embedded in web pages fail to play due to denied Cross-Origin request
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
People
(Reporter: striborgvidya, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
Steps to reproduce:
Fresh Firefox install on a new pc.
Initially suspected an add-on inherited through Firefox Sync, but the issue presents itself even in safe mode.
Every Twitter video fails to load, and imgur pages containing mp4 files just display a blank page.
Actual results:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json?keepalive=false. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://t.imgur.com/. (Reason: CORS request did not succeed). Status code: (null).
Expected results:
Videos should have played normally.
Comment 1•2 years ago
|
||
See https://support.mozilla.org/en-US/questions/1308176 and https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSDidNotSucceed .
Does this also happen when using safe mode in a complete fresh user profile with zero add-ons and zero extensions?
| Reporter | ||
Comment 2•2 years ago
|
||
Issue presents itself even in Safe Mode with a fresh profile.
| Reporter | ||
Comment 3•2 years ago
|
||
In the fresh profile's case the error message changes to:
Content Security Policy: The page’s settings blocked the loading of a resource at data:i (“object-src”).
Comment 4•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
| Reporter | ||
Comment 5•2 years ago
|
||
Further testing seems to show this applies to any site containing video content.
Youtube mostly unaffected for some reason, though some videos will rarely throw an error.
| Reporter | ||
Updated•2 years ago
|
| Reporter | ||
Comment 6•2 years ago
|
||
Issue turned out to be caused by the fresh Windows N install lacking the Windows Media Package.
Apologies for this.
Description
•