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
Originally posted by vibsid0986 August 16, 2024
Hello Team,
I was working on workflow-glsp examples and observed that when we double click on a node and Autocomplete widget opens, select all, undo and redo are not working in there, even their corresponding key bindings seems to select the complete workflow example widget instead of the text in the autocomplete widget. Please see below image when I did Ctrl + A on the node with text "ABC", it selects the complete widget.
Request you to help me in resolving this issue, as I need to implement select all, undo, redo for my custom use case.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
I didn't get to debugging this in detail, but it looks like those events are coming from Theia and are forwarded to the GLSP Theia integration, which then directly acts as if the diagram should handle those, when in fact some input field has focus and should handle those events.
I assume we need to check the GLSP Keybinding Context and only activate it if the diagram has focus, but not if an input field has focus.
This bug may have been introduced by a rather recent move of the UI extensions into the diagram container, but I'm not sure.
Discussed in #1389
Originally posted by vibsid0986 August 16, 2024
Hello Team,
I was working on workflow-glsp examples and observed that when we double click on a node and Autocomplete widget opens, select all, undo and redo are not working in there, even their corresponding key bindings seems to select the complete workflow example widget instead of the text in the autocomplete widget. Please see below image when I did Ctrl + A on the node with text "ABC", it selects the complete widget.
Request you to help me in resolving this issue, as I need to implement select all, undo, redo for my custom use case.
Thanks in advance.
The text was updated successfully, but these errors were encountered: