New issue
Advanced search Search tips

Issue 594959 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2016
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
LBS



Sign in to add a comment

LBS redirect to IE fails in incognito

Project Member Reported by kotah@chromium.org, Mar 15 2016

Issue description

Chrome Version: Latest 49.0.2623.75m (Also repro with older version, 48.0.2564.109m)
Other browsers: Any, including IE11
OS Version: Any, including Windows7
Legacy Browser Support (LBS) Version: 4.1 (Native host add-on 4.0.0.0)

LBS fails to redirect URLs in url_list with error "This webpage is not available (ERR_ADDRESS_UNREACHABLE)" to IE. Address bar shows "chrome-extension://heildphpnddilhkemkielfhnkaagiabh/action.html#{TARGET_URL}".
Screenshot from my test domain: https://drive.google.com/open?id=0B3B7SKCSXU4SNElQNndDYmhqWHc

Steps to reproduce (Issue easily reproducible with any users and any URLs)
1) Configure LBS
2) Open Chrome and enable "Allow in incognito" in chrome://extensions
3) Go to Incognito and open a URL listed in url_list

Expected behavior: LBS redirects to IE

Actual behavior: Redirect fails with error "This webpage is not available (ERR_ADDRESS_UNREACHABLE)"
 
Cc: pastarmovj@chromium.org
Julian: Do you know who owns this code now so it can get categorized and cc'd appropriately?
Cc: -pastarmovj@chromium.org
Owner: pastarmovj@chromium.org
Status: Untriaged (was: Unconfirmed)
Hi Ryan,
This will still be me :) Any LBS related issue is still my responsibility.

I don't think we ever envisioned LBS running in incognito mode but I will see if this is something we can support and if we want to support it because it poses some threats to incognito mode and come back to this thread with the analysis.
Status: Assigned (was: Untriaged)
We can enable LBS in incognito. It is a matter of updating the manifest file. I will see if there is any reason that speaks against it privacy or security wise and fix this for the next release of the extension.
Status: Fixed (was: Assigned)
After evaluating the privacy implication we decided to fix the broken behavior by disabling transitions in incognito mode. The extension can be enabled for incognito mode (with the checkbox on the extensions page) because fully disabling it for incognito will bum up the minimal supported version of Chrome too much but it will not monitor URLs typed in this mode and respectively not transition to the alternative browser. The reason for that is that when URL are transitioned to the alternative browser the privacy expectations of the incognito mode can not be guaranteed.

Sign in to add a comment