New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 737826 link

Starred by 2 users
Status: Verified
Owner:
█ asimjour@chromium.org
Last visit > 30 days ago
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

Some features rejected in VR cannot be used after exiting VR

Project Member Reported by vsupruniuk@google.com, Jun 29 2017 
Chrome Canary: 61.0.3143.0
OS: Android 7.1.2
Device: Pixel

What steps will reproduce the problem?
1. Visit https://permission.site/
2. Tap "Microphone" button and allow access to microphone. Audio access indicator should appear in Android notification area
3. Reload page to stop page access to the audio input (audio capturing indicator in Android notification area should be absent now)
4. Put device into headset, pass DON flow to enter VR
5. Click Microphone button

What is the expected result?
Audio capturing indicator should appear at the top of Browser screen

What happens instead?
Nothing happens, audio capturing doesn't started, indicator is absent

6. Exit from VR to 2D Clank, click on Microphone button again

What is the expected result?
Audio capturing indicator should appear in Android notification area

What happens instead?
Nothing happens, audio capturing doesn't started, indicator in notification area is absent

Notes:
Audio capturing indicator appears in VR as expected if to start audio capturing before entering ChromeVR (swap steps 4 and 5).

Comment 1 by ddorwin@chromium.org, Jun 29 2017

Labels: M-61
Owner: asimjour@chromium.org
Status: Assigned (was: Untriaged)
Summary: Some features rejected in VR cannot be used after exiting VR (was: Not possible to start audio capturing from ChromeVR)
[Broadening this to cover other features with the same issue.]

The results of step 5 (attempting to use a permission-allowed features in VR) are tracked for all features in  issue 738209 .

This bug now covers the result of step 6, which is that audio capture (and other features) cannot be used after exiting VR if they had previously been rejected in VR.

It appears that the following are affected:
* Notifications
* Location
* Video
* Audio

Bluetooth, USB, EME, Persistent Storage, and Quota Management all appear to work.

Comment 2 by vollick@chromium.org, Jul 10 2017

Labels: -Pri-3 Pri-2
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 11 2017

Labels: Hotlist-Google
Project Member

Comment 4 by bugdroid1@chromium.org, Jul 12 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a4e62f705de45a529006bece92f02c7a8a2dab3e

commit a4e62f705de45a529006bece92f02c7a8a2dab3e
Author: Amirhossein Simjour <asimjour@chromium.org>
Date: Wed Jul 12 02:21:56 2017

VR: Permission request in VR is not count as DENIED

When in VR, RequestMediaAccessPermission should call the callback by
MEDIA_DEVICE_NOT_SUPPORTED. As a result user can ask for the permission
outside of VR mode later.

BUG= 737826 

Change-Id: I86675bdbf832ac7bb65a74fd88f54254e0bfd931
Reviewed-on: https://chromium-review.googlesource.com/567482
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485800}
[modify] https://crrev.com/a4e62f705de45a529006bece92f02c7a8a2dab3e/chrome/browser/android/tab_web_contents_delegate_android.cc

Comment 5 by asimjour@chromium.org, Jul 12 2017

Status: Started (was: Assigned)
The only remaining one is geolocation permission, that uses PermissionManager.

Comment 6 by asimjour@chromium.org, Jul 13 2017

Status: Fixed (was: Started)
I'm oing to close this and open a new one only for geolocation permission.

Comment 7 by dbbrooks@chromium.org, Jul 26 2017

Status: Verified (was: Fixed)
Verified in chrome 62.0.3166.3
►

Sign in to add a comment