[Webkit-unassigned] [Bug 165251] New: add runtime flags for getUserMedia and RTCPeerConnection and set them to off in Safari Tech Preview until stable enough
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Dec 1 04:42:06 PST 2016
https://bugs.webkit.org/show_bug.cgi?id=165251
Bug ID: 165251
Summary: add runtime flags for getUserMedia and
RTCPeerConnection and set them to off in Safari Tech
Preview until stable enough
Classification: Unclassified
Product: WebKit
Version: Safari Technology Preview
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Bindings
Assignee: webkit-unassigned at lists.webkit.org
Reporter: agouaillard at gmail.com
CC: cdumez at apple.com
It has been brought to my attention that apparently Safari Tech Preview Release 18 (Safari 10.1, WebKit 12603.1.12) is exposing RTCPeerConnection and navigator.mediaDevices.getUserMedia.
Since a check for
navigator.mediaDevices.getUserMedia && window.RTCPeerConnection
and redirecting browsers that support neither is pretty common this is rather unfortunate.
The getUserMedia implementation does not seems to work on one of the most basic GUM samples at
https://webrtc.github.io/samples/src/content/getusermedia/gum/
I am actually not seeing GUM resolve or reject the promise at all.
And RTCPeerConnection did not work either in
https://webrtc.github.io/samples/src/content/peerconnection/pc1/
What is the plan here?
Philipp
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161201/7db58645/attachment-0001.html>
More information about the webkit-unassigned
mailing list