-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop dispatching to keybindings in editing coposition text. #6673
Stop dispatching to keybindings in editing coposition text. #6673
Conversation
@502647092 Does it fix the issue for you? Could you check please? |
Does it prevent Monaco from receiving composition events? From code it seems that it expects to receive and have special handling logic, i.e. like here microsoft/vscode@31c7e3b Why is not enough to let Monaco to deal with it? |
And @mouse484 also will be one of the important reviewer. |
Expected behavior 👍 This makes Theia and its associations better for those who need IME. |
@akosyakov I cannot be sure as I'm not a Monaco specialist. The similar issue was raised on VSCode also and fixed by microsoft/vscode#40546. |
@502647092 Hmm... I'm using Japanese IME on ChromeOS and it looks working well. |
@monaka |
We need to catch up with Monaco then. Maybe it would be feasible at the beginning of next year. I would be fine though to accept this PR as a temporary solution if it works. Here is the explanation why Theia is using custom monaco-editor-core and which other packages are necessary: https://github.com/eclipse-theia/theia/wiki/LSP-and-Monaco-integration For previous update we used this branch: https://github.com/TypeFox/vscode/tree/monaco/0.18.0. We will need a new branch which is forked from latest master, tested with upstream with bug fixes provided to upstream, tree shaking should be removed as in previous version, then it should be published for testing and tested with Theia like here #5901. We have plans to work on auto testing it in mid December and next January to make Monaco migration easier. |
@akosyakov I agree it's a best to fixed by upgrading Monaco to the latest. And you might not recognized, this issue is a show-stopper to the Chinese/Japanese/Korean people. |
@502647092 What do you think? Is it better despite #6673 (comment)? @mouse484 Do you have something like #6673 (comment)? |
@akosyakov |
It may be different from this problem. |
@502647092 I understood that the freezing exists with or without this change (i.e. #6603)? |
4588241
to
49e4a20
Compare
@mouse484 It's better to raise new issue for your report, IMO. But your report is interesting to me. |
@svenefftinge #6603 was raised on 14 days ago. And this PR was raised on 4 days ago. |
Signed-off-by: Masaki Muranaka <monaka@monami-ya.com>
49e4a20
to
dfce5b5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's give it a try, at least it seems to fix some cases and we can revert it later
As always; beamers never work during the presentations and hotfixes contain typos -> |
@502647092 @mouse484 It would help if you also give it a try: #6673 (comment) 🙏 |
not Fixed in Japanese IME (Works before removing the fix - 32b26b2) |
thanks, will try to reproduce it on my machine and investigate it. |
Signed-off-by: Masaki Muranaka monaka@monami-ya.com
What it does
Ignores
keydown
event when IME is working.This will fix #6459 and gitpod-io/gitpod#875 .
How to test
Editing texts like the description of #6459.
Review checklist
Reminder for reviewers
This patch was tested on my Chrome only.
I suppose this will work also on another modern browsers, but not tested on them.