Comment 6 for bug 1563398

Peter, we couldn't land pre-release builds of Oxide 1.15, which is the release where those fixes were developed and tested.

Oxide is on a 6 weeks release cadence, in sync with Blink upstream, and that not always allows us to make it into the target OTAs. Between features and stability / security, we always opt for the latter.

Oxide 1.15 builds are available at https://launchpad.net/~oxide-builds/+archive/ubuntu/oxide-next
Next is generally ok on a developer's phone, whereas trunk is not really recommended unless you develop on Oxide itself.

With Oxide 1.15 you get the getUserMedia API that lets apps change the capture devices dynamically. This is what we expect WebRTC applications to use in the future.

The case of appear.in is that they don't use this API (yet?) and rely on the "user agent" to switch between cameras. There is such a feature already in webbrowser-app, where you can switch cameras, the same way the FAQ advises to workaround the problem on Microsoft Surface.

We definitely want all new WebRTC apps to run great on Ubuntu, ie not just Google Hangouts. T