In incognito mode, chrome.contentSettings.microphone does not inherit the regular settings
Reported by
cool...@gmail.com,
Apr 14 2018
|
||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 Steps to reproduce the problem: 1. install the attached extension. 2. give the extension permission to run in incognito mode. 3. open the chrome browser in the regular mode. 4. navigate to chrome-extension://EXTENSION_ID/coolcmd.html 5. open the F12 console. 6. open the chrome browser in the incognito mode. 7. navigate to chrome-extension://EXTENSION_ID/coolcmd.html 8. open the F12 console. What is the expected behavior? Console content in regular mode: OK get regular contentSettings: allow get incognito contentSettings: You do not have permission to access incognito preferences. access to audio devices is allowed Console content in incognito mode: get regular contentSettings: allow get incognito contentSettings: (i do not know, but definitely not permission error) access to audio devices is allowed Inheritance documentation: https://developer.chrome.com/extensions/contentSettings#type-Scope What went wrong? Console content in regular mode: OK get regular contentSettings: allow get incognito contentSettings: You do not have permission to access incognito preferences. access to audio devices is allowed Console content in incognito mode: get regular contentSettings: ask get incognito contentSettings: You do not have permission to access incognito preferences. access to audio devices is blocked Did this work before? Yes 49 Does this work in other browsers? N/A Chrome version: 66.0.3359.66 (Официальная сборка) beta (64 бит) (cohort: Beta) Channel: beta Channel: beta OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: With this and 832697 issues, there is impossible to select audio output device in incognito mode.
,
Apr 16 2018
,
Apr 16 2018
I believe this is working as intended. We changed content setting inheritance some time ago to not inherit settings that are more permissive than the default. The other bug about Chrome crashing when requesting the incognito permission is definitely a bug. We should probably still update the documentation.
,
Apr 16 2018
dullweber@, why in incognito mode chrome.contentSettings.microphone.get({incognito:true}) returns permission error? this is bug.
,
Apr 17 2018
Able to reproduce this issue on reported version 65.0.3325.181, on latest canary 68.0.3397.0 using Windows 10, Mac 10.13.3 and Ubuntu 14.04. i.e; Observing get regular contentSettings: ask get incognito contentSettings: You do not have permission to access incognito preferences. access to audio devices is blocked in Incognito mode. This issue is seen from M-60. Hence considering this issue as Non-Regression and marking as Untriaged. Thanks!
,
Apr 17 2018
,
Apr 23 2018
Assigning owner. Please reassign if needed.
,
Apr 24 2018
I think the inheritance behavior is correct but chrome.contentSettings.microphone.get({incognito:true}) shouldn't return a permission when in incognito mode.
I guess we can remove the target milestone as this is not a recent regression.
,
Jun 6 2018
Reassigning to Ramin. Maybe the recent change has already solved the permission error?
,
Jun 7 2018
The permission error is already fixed in crbug.com/832697 . The permission change from "allow in regular" to "ask in incognito" is the intended behavior as we reduce all given permissions to minimum of user selection in regular and default value. So I think we can close this bug. Am I missing anything?
,
Jun 7 2018
rhalavati@, https://bugs.chromium.org/p/chromium/issues/detail?id=833061#c3 "We should probably still update the documentation."
,
Jun 7 2018
Thanks, then I will mark this is fixed, and start a thread to update the documentations. |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Apr 15 2018