You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When typing brave://settings and chrome://settings in private window's omnibox,
both shows different result.
brave://settings is opened in private window and chrome://settings is opened in normal window.
Steps to Reproduce
Typing brave://settings and chrome://settings in private window's omnibox
Check the opened window (private or normal window)
Actual result:
Both are opened in different window.
brave://settings is opened in private window.
chrome://settings is opened in normal window.
Expected result:
Both should be opened in normal window.
Reproduces how often:
Always.
Brave version (brave://version info)
All current channels.
Reproducible on current release:
Does it reproduce on brave-browser dev/beta builds?
Yes
Website problems only:
Does the issue resolve itself when disabling Brave Shields? No
Is the issue reproducible on the latest version of Chrome? No
Additional Information
Mapping from brave to chrome is not applied when page is checked whether allowed in private window or not.
The text was updated successfully, but these errors were encountered:
Description
When typing brave://settings and chrome://settings in private window's omnibox,
both shows different result.
brave://settings is opened in private window and chrome://settings is opened in normal window.
Steps to Reproduce
Actual result:
Both are opened in different window.
brave://settings is opened in private window.
chrome://settings is opened in normal window.
Expected result:
Both should be opened in normal window.
Reproduces how often:
Always.
Brave version (brave://version info)
All current channels.
Reproducible on current release:
Yes
Website problems only:
Additional Information
Mapping from brave to chrome is not applied when page is checked whether allowed in private window or not.
The text was updated successfully, but these errors were encountered: