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

Issue 813858 link

Starred by 5 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression
Team-Security-UX



Sign in to add a comment

Cant get the mic due to policy change.

Reported by gcl...@gmail.com, Feb 20 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36

Steps to reproduce the problem:
1. Open in iframe a web application that has a mic feature to accept speech. 
2. click on mic to start speaking.
3. immediately you will get error in console log saying "AudioCapture permission has been blocked because of a Feature Policy applied to the current document. See https://goo.gl/EuHzyv for more details."

What is the expected behavior?
it should ask for mic Allow/deny permission.

What went wrong?
updated to V64 and this feature stopped working.

Did this work before? Yes V63

Does this work in other browsers? Yes

Chrome version: 64.0.3282.167  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 

Comment 1 by gcl...@gmail.com, Feb 20 2018

This issue is very similar to the other cases but it has mainly talking of hanngout issue. 

opened this new case for browser based application rendering in iframe and has mic features.

https://bugs.chromium.org/p/chromium/issues/detail?id=797080

Comment 2 by gcl...@gmail.com, Feb 20 2018

Tried with the option of allow=microphone attribute as per recommendation at https://goo.gl/EuHzyv  but that not helping either.
Labels: Needs-Triage-M64
Labels: Needs-Bisect
Cc: krajshree@chromium.org
Components: Blink>GetUserMedia>Mic
Labels: Triaged-ET Needs-Feedback
Reporter@ - Thanks for filing the issue...!!

Could you please provide a sample test file/url to test the issue from TE-end.
This will help us in triaging the issue further.

Thanks...!!

Comment 6 by phistuck@gmail.com, Feb 21 2018

If you could share a URL that reproduces the issue, it will expedite the diagnosis and probably the fix.

Comment 7 by olka@chromium.org, Feb 21 2018

Owner: guidou@chromium.org
Status: Assigned (was: Unconfirmed)
guidou@ could you PTAL?

Comment 8 by gcl...@gmail.com, Feb 21 2018

Its hard for me to give you a url to reproduce it. This happens only when the application renders in iframe. can you pls send email to my email id attached to this and i will share my contact details, i can show you help reproduce the issue. 

Comment 9 by phistuck@gmail.com, Feb 21 2018

If you can reproduce this via JSFiddle, JSBin or even GitHub (you can place one page on GitHub Pages and show an iFrame from rawgit.com).
If I reproduce this, I could mark this as untriaged, but I will not be fixing this (I am just triaging issues), which is why a public URL will be much more helpful.
Cc: guidou@chromium.org
Components: -Blink>GetUserMedia>Mic Internals>Permissions Blink>FeaturePolicy
Owner: ----
Status: Untriaged (was: Assigned)
Switching to better components for further triaging.
Cc: raymes@chromium.org iclell...@chromium.org
It may be helpful to share a snippet of the <iframe> tag from your html. In particular, adding allow="microphone" will only grant microphone access to the URL specified in the src= attribute if the <iframe>. If you want to grant it to a different URL that gets loaded in the iframe, you must specify something like allow="microphone https://example.com" or allow="microphone *" for all origins.

Comment 12 by gcl...@gmail.com, Feb 22 2018

I tried the "microphone *" option and it didnt work as well. 
Thanks. We'll need you to provide a more detailed reproduction case in order to help you, otherwise we'll just be guessing at the problem. 

Comment 14 by gcl...@gmail.com, Feb 24 2018

This issue is now resolved. Fix is to add allow=microphone in all nedted iframes.

Comment 15 by gcl...@gmail.com, Feb 24 2018

Nested iframe I meant.

Status: WontFix (was: Untriaged)
It sounds like this is working-as-intended.

Sign in to add a comment