Refs: #117621

• anyOS @rebornix
• anyOS @stevencl

Complexity: 3

Create Issue

There's a new setting explorer.enableUndo which controls how the explorer interacts with Cmd+Z. Verify:

• When warn (default), all destructive undos in the explorer are guarded by a prompt. This includes dragging a file into the explorer then undoing, pasting a folder/file and undoing, or whatever other actions you can think of.
• When allow, the behaviour of the existing stable is maintained. Generally, this tries to warn when the destruction would be less-expected (for instance if the next item in the undo stack is a file creation, but the current Undo context isn't the explorer). The main thing to verify here is that behaviour hasn't changed since stable.
• When neverdisable, the explorer never participates in Undo operations, and undos will be routed to the DOM/editor even when focus is in the explorer.