Window trust with empty workspaces #124824
Labels
bug
Issue identified by VS Code Team member as probable bug
verified
Verification succeeded
workspace-trust
Trusted workspaces
Milestone
click on it
the tab title says 'Workspace Trust` (IMO this should become Restricted Mode, also with workspaces)
The section mentions 'In trusted window'. Good, (but should be capitalized:
Trusted Window
)It also mentions
16 workspace settings are not applied
. That's strange, how can there be workspace settings. Click on the link, there are no workspace settings . Also when I go to the settings page there are no workspace settingstrust the window, reload the window, the window is restricted again
open a new window (restricted) , use
Add folder to workspace
, choose a folder that is trusted : the window is now suddenly unrestrictedIf the restrictedness is a property of the window, then the window should keep its restricted state across reloads and operations.
If the restrictedness is a property of the workspace, then it's strange that an empty window is restricted.
The loose files brought us in the direction of restricted windows. I personally like the concept. It's similar to 'Private browsing window' on browsers. But has different traits than 'restricted workspaces'.
'restrictedness' is a window property and does not change
users can decide to open the same folder in restricted mode and in unrestricted mode. the recent history entries would reflect that. You could see the same input once with and without the
[Restricted]
tag.we can add a top level menu
File
entryNew Restricted Window
On 'Open Folder' we can still deduct based on the folder/workspace path whether to open a restricted or a normal window. But IMO that needs to be decided 'before' the window is opened (or before the window starts the ext host)
The text was updated successfully, but these errors were encountered: