Integrated browser "edit mode": use inline text edits as a signal for Copilot edits #310710 karlhorky opened 5 hours ago · edited by karlhorky When performing marketing copy edits, it is often faster to just change text copy directly in the integrated browser than to describe the change in chat and wait for Copilot to make the change and the dev server to update the integrated browser (especially true with slower dev servers). In the integrated browser, introduce a mode where DOM elements/nodes containing text are temporarily editable (eg. the behavior of contenteditable attribute). The user can then edit text inline and click on a "Save" button, upon which Copilot should use the diff of the edited text (plus nearby DOM context and innerHTML, as necessary) as a signal to propose source edits in the backing tsx / jsx / html / svelte / vue / etc file. This proposal is NOT about persisting DOM edits deterministically to files. The browser would only be the interaction surface, while Copilot still generates normal source edits for review, based on the diff. This could be extended to other non-text edits in future, such as image paths. Alternatives considered Full WYSIWYG editor, mapping changes to source files deterministically cc @meganrogge @jruales @kycutler
VS Code: I suggested an "edit mode" for the integrated browser, for WYSWYG-style workflows of changing text copy
If you also want this: it is a backlog candidate now, needs 20 👍 reactions to move it to backlog
github.com/microsoft/vs...