Preamble - this is quite a strange one. My initial starting point was that I wanted to try get YouTube to play nicely without the cookie consent modal flow being forced in private mode... This is useful when using "private browsing by default".
I have determined that visiting youtube.com and google.com with cookies disabled on a per-site basis (see below) is effective and makes this work in non-private browsing. Since a cookie can't be set, they can't handle consent, so the prompt doesn't show (as the selective routing to the cooking screen is bypassed via cookie presence).
I don't have a 100% solid explanation for the behaviour below, but can hopefully demonstrate there is a "bug" of some kind through logic.
Steps to reproduce:
(For convenience of the test, I suggest having a new private window to be default option on load). Close Orion and open it again. All extensions are disabled for this test.
- Close Orion. Open it into a private window.
- Visit youtube.com (typed "youtube.com" into location bar and hit enter)
- Notice you see the Google cookie consent screen:
- Refresh this page multiple times, as you wish, to satisfy yourself this prompt will appear every time.
- Add a restriction on cookies for www.youtube.com via Preferences > Privacy > Cookies
- Reload the youtube tab as desired. Create a new private tab, close the existing one, browse to youtube again if you wish - it will still show the consent prompt.
- Click File > New Window in Orion, to open a non-private window
- In the new window, type "youtube.com" into the location bar and hit enter
- No cookie consent prompt is shown in the non-private window (!)
- Switch back to the private window. Refresh your youtube tab. You will not see the consent prompt.
- Restart Orion.
- Visit youtube.com again, notice you get the consent prompt again.
- (Optionally) repeat step 6 onwards, to satisfy yourself this is repeatable.
This illustrates that a state change in non-private browsing (i.e. visiting the site) is able to infiuence the state of the private window session on the same site.
Since it is repeatable after you restart Orion, I don't think it's a case of using non-private browsing to "jiggle" a setting to work correctly - it looks like there is some persistence of state between private and non-private browsing.
Expected behavior:
Isolation between private and non-private browsing.
Ideally, same behaviour in private and non-private browsing - if cookies are blocked on a site, this should be honoured in private browsing mode, since blocking cookies can alter a site's behaviour beneficially (like in this case).
Orion, OS version; hardware type:
Version 0.99.109.1.5-beta
Image/Video: