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
EditorWidget has a handler for onSelectionChanged that updates the global selection to the current editor. However, that code does not fire if the user switches editors without moving the cursor in the new editor.
update the when statement in the package.json in contributes -> menus -> editor/title to:
"resource =~ /^(.)/pages/(.)$/ && editorLangId == json && editorFocus == true"
Build it: npm run package and add it as extension to Theia
Create a .json file on the root folder
Create a 'pages' folder and create another .json file in this folder
Open both files side by side
Move the cursror in the JSON file.
Observe that the icon appears for the JSON file.
Activate the markdown editor without moving the cursor.
Observe that the icon still appears
Additional Information
Operating System: RHEL
Theia Version: master (2/8/2021)
The text was updated successfully, but these errors were encountered:
Bug Description:
EditorWidget
has a handler foronSelectionChanged
that updates the global selection to the current editor. However, that code does not fire if the user switches editors without moving the cursor in the new editor.Steps to Reproduce:
(see #9013)
Clone https://github.com/avishaik/vscode-editor-btn-bug
update the when statement in the package.json in contributes -> menus -> editor/title to:
"resource =~ /^(.)/pages/(.)$/ && editorLangId == json && editorFocus == true"
Build it:
npm run package
and add it as extension to TheiaCreate a .json file on the root folder
Create a 'pages' folder and create another .json file in this folder
Open both files side by side
Move the cursror in the JSON file.
Observe that the icon appears for the JSON file.
Activate the markdown editor without moving the cursor.
Observe that the icon still appears
Additional Information
master
(2/8/2021)The text was updated successfully, but these errors were encountered: