ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

The problem here is that the site detects Chrome by doing "if
(navigator.webkitGetUserMedia && !!window.chrome)", and that makes it
use navigator.webkitGetUserMedia on Chrome (which also exists on Oxide)
- This detection is obviously broken on Oxide because window.chrome
doesn't exist.

navigator.getUserMedia doesn't exist in Oxide (and neither does it in
Chrome), but this API and Chrome's prefixed version of it is deprecated
in any case. Oxide does support the replacement
navigator.mediaDevices.getUserMedia.

So this is a website bug

** Changed in: oxide
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1505746

Title:
  Enable WebRTC functions

Status in Oxide:
  Invalid

Bug description:
  I opened https://apprtc.appspot.com/ in webbrowser-app running on
  arale with oxide 1.10.2, and it appears some WebRTC functions are not
  being exposed:

      Error getting user media: getUserMedia is not a function

      Create PeerConnection exception: RTCPeerConnection is not a
  function

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1505746/+subscriptions