camera getUserMedia() from jsfiddle.net broken in Nightly (NotReadableError)
Categories
(Core :: Permission Manager, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox66 | --- | unaffected |
firefox67 | --- | unaffected |
firefox68 | - | fixed |
People
(Reporter: jib, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 obsolete file)
STRs
- Open https://jsfiddle.net/jib1/r60bzmrs/
- Allow camera permission
Expected result:
Self view.
Actual result:
NotReadableError: Failed to allocate videosource
Regression range:
7:47.26 INFO: No more inbound revisions, bisection finished.
7:47.26 INFO: Last good revision: 55089d0bf0701221a363514e12592e8bc07405db
7:47.26 INFO: First bad revision: 0229d5353d503441ed11643c8e5e4e90011261b8
7:47.26 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=55089d0bf0701221a363514e12592e8bc07405db&tochange=0229d5353d503441ed11643c8e5e4e90011261b8
Points to Bug 1330467.
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
Note I have privacy.firstparty.isolate
set to false
(the default).
Reporter | ||
Comment 2•5 years ago
|
||
As I recall NotReadableError
can be caused by the parent process permission double-check.
Comment 3•5 years ago
|
||
Why is this not covered by tests?
[Tracking Requested - why for this release]:
Can't request WebRTC permission in iframes
We could probably fix this, I haven't looked into it yet, but I wonder if landing bug 1330467 right before soft freeze might have been a mistake. Gary, do you think we should try to back out 1330467 while we still can instead of spending our time uplifting fixes to Beta? I'm kind of on the fence here.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 4•5 years ago
|
||
(In reply to Johann Hofmann [:johannh] from comment #3)
We could probably fix this, I haven't looked into it yet, but I wonder if landing bug 1330467 right before soft freeze might have been a mistake. Gary, do you think we should try to back out 1330467 while we still can instead of spending our time uplifting fixes to Beta? I'm kind of on the fence here.
OK, I agree this was more risky than I expected while the breakage occurs even when FPI is disabled.
I'll request to back out bug 1330467 and re-land into v59.
Comment 5•5 years ago
|
||
Fixed by backout: https://hg.mozilla.org/mozilla-central/rev/3866561a7bae97a6c9ec3c18174747ec36bba090
Comment 6•5 years ago
|
||
Updated•5 years ago
|
Updated•2 years ago
|
Description
•