- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Jul 2018 21:48:52 +0000
- To: public-webrtc-logs@w3.org
We had that for getusermedia for a while - Chrome didn't require secure context while Firefox did (I think that was the way it went). It led to some pages (in particular demos) that worked in one but not the other. I wouldn't be opposed to just encoding the state of the art and marking RTCPeerConnection as [[SecureContext]]. draft-ietf-rtcweb-security-10 gives rather strong arguments why loading from an HTTP origin or using mixed sources is foolish, but doesn't seem to contain a mandate for secure contexts (or I missed it); it would be nice to mandate not being foolish. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1945#issuecomment-407907646 using your GitHub account
Received on Wednesday, 25 July 2018 21:48:54 UTC