133
edits
(→Related Work: link to a list of PB consumers) |
(Added proposed behaviour) |
||
| Line 15: | Line 15: | ||
There are going to be some UI changes, of course, but they’re going to be minimal. The visual change is this: every new session is visually distinct. It will have a different colour (from purple to orange, blue, green, etc.) and also a little number to further distinguish it from each other. Everything else remains exactly the same. | There are going to be some UI changes, of course, but they’re going to be minimal. The visual change is this: every new session is visually distinct. It will have a different colour (from purple to orange, blue, green, etc.) and also a little number to further distinguish it from each other. Everything else remains exactly the same. | ||
==Proposed Behaviour== | |||
===In normal window/tab=== | |||
* Clicking ''Open Link in New Tab'' or ''Open Link in New Window'' will open content using the current session | |||
* Clicking ''File → New Private Session'' or right-clicking ''Open Link in New Private Session'' will open a fresh AppID | |||
* Every new Private Session opened from a link originating in normal window/tab gets a fresh AppID, even if the link is the same | |||
===In a private session window/tab== | |||
* Clicking on a link, or right-clicking ''Open Link in New Tab'' or ''Open Link in New Window'' will open content using the current AppID | |||
* There is no way to open a fresh AppID by right-clicking a link | |||
* The only way to open a fresh AppID is by selecting ''File → New Private Session'' | |||
* We could, perhaps, try a right-click option called ''Open Link in New Session'', but this would be confusing the distinction between private session/window/tab | |||
==Possible timeline== | ==Possible timeline== | ||
edits