Closed
Bug 1329824
Opened 8 years ago
Closed 8 years ago
Add pref to disable too-high res check on Windows
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
RESOLVED
FIXED
mozilla53
Tracking | Status | |
---|---|---|
firefox53 | --- | fixed |
People
(Reporter: mozbugz, Assigned: mozbugz)
References
Details
Attachments
(1 file)
Bug 1176218 introduced a hard-coded check for high resolutions: https://hg.mozilla.org/mozilla-central/rev/4429c8701a84 This was based on Microsoft's documentation stating that it can at most handle 4096x2304 in Win>7, and other similar constraints: https://msdn.microsoft.com/en-us/library/windows/desktop/dd797815(v=vs.85).aspx This obviously prevents 8K videos from playing on Windows. But we should allow an escape hatch for people living on the edge, and just testing, in case Windows can in fact handle 8K (maybe it really depends on the installed drivers?) So I will add a preference to disable this check.
Comment hidden (mozreview-request) |
Comment 2•8 years ago
|
||
mozreview-review |
Comment on attachment 8826985 [details] Bug 1329824 - media.wmf.allow-unsupported-resolutions - https://reviewboard.mozilla.org/r/104780/#review105512
Attachment #8826985 -
Flags: review?(jyavenard) → review+
Pushed by gsquelart@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/92383422009d media.wmf.allow-unsupported-resolutions - r=jya
Comment 4•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/92383422009d
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox53:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
thanks a lot for this. anyway, for me it doesn't seem to work. as soon as i set media.wmf.allow-unsupported-resolutions to true firefox cannot play h264 videos anymore, at least @youtube. their test site https://www.youtube.com/html5 clearly shows both H.264 and MSE & H.264 get disabled. as soon as i set the pref back to false the h264 support is backagain. tested with 53.0a2 (2017-01-26) (32-Bit) on windows 7 in a fresh profile.
You need to log in
before you can comment on or make changes to this bug.
Description
•