about:support shows "Unsupported" for Opus
Categories
(Core :: Audio/Video, defect)
Tracking
()
People
(Reporter: jrmuizel, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
37.92 KB,
application/octet-stream
|
Details |
STR:
- Start Firefox
- Load about:support
In the attached about:support most of the codecs are incorrectly reported as unsupported.
Updated•1 year ago
|
![]() |
||
Comment 1•1 year ago
|
||
If this was shortly after startup, that's a known issue. We delay recording the information here for startup perf reasons.
Reporter | ||
Comment 2•1 year ago
|
||
(In reply to Jim Mathies [:jimm] from comment #1)
If this was shortly after startup, that's a known issue. We delay recording the information here for startup perf reasons.
Why can't we gather it when about:support is loaded?
Comment 3•1 year ago
|
||
For me this isn't just a display issue in about:support. Each of the codecs listed as "Unsupported" don't work.
It shows up as unsupported and stays that way long after startup.
If I try another Firefox profile (existing, or new one), it shows up as supported, and indeed works.
When I created a new profile, it took a while for the "Codec Support Information" to appear, but once it did, it was all marked as supported.
Mozregression says it started somewhere on January 14, but these commits don't seem related:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b24d63d72f77a64fe5d8bce6420b88e7e0c4d9da&tochange=377bd4a0d4f84e30283bc5ea1048330eb05e04f1
Comment 4•1 year ago
|
||
Based on comment #3, this bug contains a bisection range found by mozregression. However, the Regressed by
field is still not filled.
:smolnar, since you are the author of the changes in the range, if possible, could you fill the Regressed by
field and investigate this regression?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Description
•