Closed Bug 849497 Opened 8 years ago Closed 8 years ago

Enable getUserMedia in xulrunner

Categories

(Toolkit Graveyard :: XULRunner, defect)

defect
Not set
normal

Tracking

(firefox20 fixed, firefox21 fixed, firefox22 fixed)

RESOLVED FIXED
mozilla22
Tracking Status
firefox20 --- fixed
firefox21 --- fixed
firefox22 --- fixed

People

(Reporter: glandium, Assigned: glandium)

Details

Attachments

(1 file)

No description provided.
Attachment #723053 - Flags: review?(benjamin)
Attachment #723053 - Flags: review?(benjamin) → review+
https://hg.mozilla.org/mozilla-central/rev/3630976c4dd9
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
Comment on attachment 723053 [details] [diff] [review]
Enable getUserMedia in xulrunner

[Approval Request Comment]
User impact if declined: getUserMedia unavailable in xulrunner applications, and in Firefox-on-xulrunner.
Risk to taking this patch (and alternatives if risky): NPOTB
String or UUID changes made by this patch: None
Attachment #723053 - Flags: approval-mozilla-aurora?
Attachment #723053 - Flags: approval-mozilla-beta?
Comment on attachment 723053 [details] [diff] [review]
Enable getUserMedia in xulrunner

a=NPOTB would work here too :)
Attachment #723053 - Flags: approval-mozilla-beta?
Attachment #723053 - Flags: approval-mozilla-beta+
Attachment #723053 - Flags: approval-mozilla-aurora?
Attachment #723053 - Flags: approval-mozilla-aurora+
Such a minor change not tested at all in the Beta channel might generate in Release AMD Radeon crashes (see bug 772330) that are sensitive to any shifts in code addresses. Remember bug 830531 in 19.0.
(In reply to Scoobidiver from comment #7)
> Such a minor change not tested at all in the Beta channel might generate in
> Release AMD Radeon crashes (see bug 772330) that are sensitive to any shifts
> in code addresses. Remember bug 830531 in 19.0.

What is enabled here for xulrunner is already enabled in firefox. There is nothing untested here.
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.