Skip to content

Custom editor reopened from untitled does not properly wire in dirty state? #125293

@bpasero

Description

@bpasero

Steps to Reproduce:

  1. open an untitled text editor and type some content
  2. reopen with hex editor

=> the editor indicates dirty, but e.g. the explorer does not

From my testing it seems like in this case the working copy that is created does not emit a onDidChangeDirty event?

recording (2)

Metadata

Metadata

Labels

bugIssue identified by VS Code Team member as probable bugcustom-editorsCustom editor API (webview based editors)help wantedIssues identified as good community contribution opportunitiesinsiders-releasedPatch has been released in VS Code InsidersverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions