Hi Philipp,

Thanks for bringing that up.
I think we should add runtime flags for getUserMedia and RTCPeerConnection
and set them to off in Safari Tech Preview until stable enough.

    y


Le mer. 30 nov. 2016 à 14:40, Philipp Hancke <fi...@appear.in> a écrit :

> 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
> _______________________________________________
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Reply via email to