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

Issue 803724 link

Starred by 8 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug
Team-Security-UX



Sign in to add a comment

Regression: Cannot change site settings only for the current incognito session.

Project Member Reported by patricia...@chromium.org, Jan 19 2018

Issue description

Chrome Version       : 63.0.3239.132
OS Version: All Desktop Chrome (Win, Linux, Mac, CrOS)
URLs (if applicable) : N/A
Other browsers tested: N/A

What steps will reproduce the problem?
1. Open a new incognito browsing window and navigate to a site (e.g. https://www.google.com)
2. Try to enable any permission (e.g. location) without being prompted to do so.
3.

What is the expected result?
There should be an easier way to change default settings without permission prompts for the current incognito session.

What happens instead of that?
There isn't really any way to do this currently, since opening Site Details for an incognito window takes the user to the non-incognito Site Details.


This regression occurred after the removal of factory-default permissions ( Issue 657267 ) from Page Info. raymes@ suggested that "Perhaps clicking "Site settings" from an incognito tab should bring up an incognito-specific site settings window." (See  Issue 657267 , #c79, or from #c69 for more context.)

A workaround that can be used in the meantime is the following, courtesy of raymes@:

1. Open an incognito window
2. Navigate to chrome://settings/content/flash
3. Click "Add" under Allow or Block
4. Enter the URL and check "Current incognito session only"
 
Project Member

Comment 1 by sheriffbot@chromium.org, Yesterday (46 hours ago)

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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

Sign in to add a comment