Comment 0 for bug 1554244

Revision history for this message
Peter Bittner (peter-bittner) wrote :

When a web site uses WebRTC for video conferencing the webbrowser-app accesses the rear camera by default. The user can switch cameras via Settings -> Privacy & permissions -> Camera & Microphone. Unfortunately, changing this setting doesn't immediately have effect on the open web page. You have to reload the page first, which is not intuitive.

Tested / discovered with bq Aquaris E5 Ubuntu Edition, OTA-9.1 (vegeta, latest stable as of today).

Additional question: How can switching cameras be handled in web apps (driven by the webapp-container binary)? The webapp-container does neither provide a feature to specify a (different) default camera nor an interactive possibility to do so. An API call to switch cameras would be awesome.

Expected Behavior
-----------------

- Switching cameras via the settings immediately has effect on the camera used by web sites open in the webbrowser-app.
- Specifying a default camera (startup settings) is available with the webapp-container binary.
- Switching cameras programmatically (via an API call) and/or interactively is possible in web apps driven by the webapp-container.

How to Reproduce
----------------

1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default webbrowser-app)
2.) When prompted for "Allow this domain access the camera and microphone" choose "Yes"
3.) Click away the chat window (touch the down-arrow at right lower corner)
4.) Touch the screen to dismiss the "help text" (the video captured by the rear camera is shown)
5.) In the browser address bar got to Menu -> Settings -> Privacy & permissions -> Camera & Microphone, and switch to the front camera; go out of the menu going back the hierarchy; the rear camera video is still shown
6.) Tap the address bar, tap on the "Reload" icon to reload the page; the front camera video is finally shown

Other Details
-------------

- https://github.com/bittner/appear-in/issues/1 (conversion demonstrating users are confused about browser behavior)