You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
const value = /* set from `myEditor.getModel()`: */ `function hello() {
alert('Hello world!');
}`;
// Hover on each property to see its docs!
const myEditor = monaco.editor.create(document.getElementById("container"), {
value,
language: "javascript",
automaticLayout: true,
});
myEditor.onDidChangeConfiguration((e) => {
alert("Config changed!")
});
Reproduction Steps
Add handler for onDidChangeConfiguration
In Monaco Editor, click Ctrl + M to change tab focus mode
Observe that an event is not raised for onDidChangeConfiguration, but the tab focus mode is changed in the editor
Actual (Problematic) Behavior
The handler for onDidChangeConfiguration is not called.
Expected Behavior
The handler for onDidChangeConfiguration should be called
Additional Context
This issue seems to have originated from 0.36.0. May be related to this bug:
Reproducible in vscode.dev or in VS Code Desktop?
Reproducible in the monaco editor playground?
Monaco Editor Playground Link
https://microsoft.github.io/monaco-editor/playground.html?source=v0.52.0#XQAAAAKqAQAAAAAAAABBqQkHQ5NjdMjwa-jY7SIQ9S7DNlzs5W-mwj0fe1ZCDRFc9ws9XQE0SJE1jc2VKxhaLFIw9vEWSxW3yscwzzSoHfGetpg8d5BCIdogK6CBmgyKHIOVjH6uO-oA-RA-rcpQdGBlgwMT7NDeGjyzFr76MYz0c_YZhkfVact66KR8C292eYPotyrTpNzU4R2pnsg0qMoJFMwW0-anHTtAsGYd8vCeUpVswYFrP72raJqV9anqkd1j9jzqyU9LIcX7Tsw5ZHju14bgnXGT_1jFdi35F53qgwGQlYCxtuQo0E9RLxQwABNyr8p0Pk9P1BV_WsoxPSlyClyFxkPHtujBEuyUl7I-AMd-ICfjOGnF4hktGqtJD2U2lW4tZcb2_1CP5P34uuI9YAXpiZnr-04nkjRaUEVYGWGCySabpG-IJwPL_5BqO9SEQfiX-n7D0A
Monaco Editor Playground Code
Reproduction Steps
onDidChangeConfiguration
onDidChangeConfiguration
, but the tab focus mode is changed in the editorActual (Problematic) Behavior
The handler for
onDidChangeConfiguration
is not called.Expected Behavior
The handler for
onDidChangeConfiguration
should be calledAdditional Context
This issue seems to have originated from 0.36.0. May be related to this bug:
#1493
The text was updated successfully, but these errors were encountered: