New issue
Advanced search Search tips

Issue 592014 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Expose IncognitoModeAvailability to Chrome Extension

Reported by teddy@proctorio.com, Mar 4 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36

Steps to reproduce the problem:
1. Use registry or group policy to remove Incognito from Chrome (IncognitoModeAvailability = 0)
2. From Chrome extension, call chrome.extension.isAllowedIncognitoAccess, the result is false

What is the expected behavior?
A means of determining if IncognitoModeAvailability is on or off

What went wrong?
isAllowedIncognitoAccess will always be false if there is no IncognitoModeAvailability. This creates a logic hole for our use case. In certain situations our extension must be aware of all windows and tabs - this can be true even when isAllowedIncognitoAccess is false. 

If the browser is not allowed to be in incognito, then isAllowedIncognitoAccess is not applicable.

Propose adding: chrome.incognitoModeAvailability. This could be checked to ensure the user does have the ability to create incognito windows. For our use case, we would not need to check chrome.extension.isAllowedIncognitoAccess which currently gives us a false reading for what we are trying to accomplish.

WebStore page: 

Did this work before? No 

Chrome version: 48.0.2564.116  Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 20.0 r0
 
Cc: rdevlin....@chromium.org
Can you provide a little more detail on what your use case is, and why the difference matters?

Comment 2 by teddy@proctorio.com, Apr 29 2016

The use case is where an extension requires access to all tabs, incognito or otherwise.

This could be a simple bool, true/false, whether or not all tabs and windows are accessible. 
1. Incognito access is not allowed, IncognitoModeAvailability allows an incognito window to be created => false
2. Incognito access is allowed, IncognitoModeAvailability allows an incognito window to be created => true
3. Incognito access is not allowed, IncognitoModeAvailability prevents an incognito window to be created => true

Case 3 is currently impossible to determine from a chrome extension. When IncognitoModeAvailability is false, then isAllowedIncognitoAccess is also false. 

In a use case, where all tabs and windows must be accessed checking isAllowedIncognitoAccess provides a "false negative".

Does that help?
Project Member

Comment 3 by sheriffbot@chromium.org, May 1 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment