IME Keyboard imput appears in an unexpected location for the WPF browser.
726 views
Skip to first unread message
Michael M
Jun 28, 2015, 10:33:23 PM6/28/15
to cefs...@googlegroups.com
Hey all.
We are currently using CefSharp.WPF in our application. One of the requirements is the ability to accept IME input.
Looking at the code in the CefSharp.Wpf.Example, I was able to get it working, but our testers have issue with the fact that the IME dialog appears at the top of the page, rather than where the cursor is.
Trawling through the issues, I know there were issues with the actual acceptance of IME keys, but I haven't found anything pertaining to the positioning of the IME dialog.
The closest I've found was this issue : https://bitbucket.org/chromiumembedded/cef/issue/798/out-of-focus-while-entering-ime , but that was related to Chromium itself, and the latest test builds seem to work fine (as does the WinForms demo).
For the record, I'm using the version 41 nuget package.
Let me know if you need more information.
We are currently using CefSharp.WPF in our application. One of the requirements is the ability to accept IME input.
Looking at the code in the CefSharp.Wpf.Example, I was able to get it working, but our testers have issue with the fact that the IME dialog appears at the top of the page, rather than where the cursor is.
Trawling through the issues, I know there were issues with the actual acceptance of IME keys, but I haven't found anything pertaining to the positioning of the IME dialog.
The closest I've found was this issue : https://bitbucket.org/chromiumembedded/cef/issue/798/out-of-focus-while-entering-ime , but that was related to Chromium itself, and the latest test builds seem to work fine (as does the WinForms demo).
For the record, I'm using the version 41 nuget package.
Let me know if you need more information.
Alex Maitland
Jul 1, 2015, 4:56:11 AM7/1/15
to cefs...@googlegroups.com
https://bitbucket.org/chromiumembedded/cef/issue/1610/ime-not-positioned-correctly-in-windows
https://bitbucket.org/chromiumembedded/cef/issue/1377/windows-ime-window-can-not-close-when
Both have been fixed in `2357` (Version `43`) for which there is no corresponding `CefSharp` version yet. Hopefully there will be in the near future.
https://bitbucket.org/chromiumembedded/cef/issue/1377/windows-ime-window-can-not-close-when
Both have been fixed in `2357` (Version `43`) for which there is no corresponding `CefSharp` version yet. Hopefully there will be in the near future.
Michael M
Jul 1, 2015, 7:55:26 AM7/1/15
to cefs...@googlegroups.com
Thanks for replying.
So the WPF version manifest itself differently ?
I observed the described issue in the WinForms example (IME at bottom right), but it eventually appeared near the cursor, so figure it was a problem unique to the WPF version.
So the WPF version manifest itself differently ?
I observed the described issue in the WinForms example (IME at bottom right), but it eventually appeared near the cursor, so figure it was a problem unique to the WPF version.
Alex Maitland
Jul 1, 2015, 8:11:38 AM7/1/15
to cefs...@googlegroups.com
It's possible that it's WPF specific. Easiest way to test is to grab a copy of the `CEF` reference application `cefclient`.
Some basic information can be found at https://github.com/cefsharp/CefSharp/blob/master/CONTRIBUTING.md#cefsharp-vs-cef
If you grab the latest `2272` build as a starting point, if the problem persists then it's likely an upstream issue.
Then grab the latest `2357` build which should contain the fixes. Hopefully upgrading to a newer version resolves the issue.
Some basic information can be found at https://github.com/cefsharp/CefSharp/blob/master/CONTRIBUTING.md#cefsharp-vs-cef
If you grab the latest `2272` build as a starting point, if the problem persists then it's likely an upstream issue.
Then grab the latest `2357` build which should contain the fixes. Hopefully upgrading to a newer version resolves the issue.
Jørn Hansen
Jul 1, 2015, 8:59:39 AM7/1/15
to cefs...@googlegroups.com
Alex,
the #cefsharp-vs-cef questing looks like it could now merit being one of the items in the FAQ ... I've noted you and others far too often have to point that out (which gets tiresome).
Do you think there is another FAQ item that we can retire by now? Wold be nice to stay within the base-10 limit ... even tough for software related stuff like CefSharp is we can always switch to base-16 aka hexadecical ... lol!
Thoughts?
/Jorn
the #cefsharp-vs-cef questing looks like it could now merit being one of the items in the FAQ ... I've noted you and others far too often have to point that out (which gets tiresome).
Do you think there is another FAQ item that we can retire by now? Wold be nice to stay within the base-10 limit ... even tough for software related stuff like CefSharp is we can always switch to base-16 aka hexadecical ... lol!
Thoughts?
/Jorn
Alex Maitland
Jul 2, 2015, 4:46:57 AM7/2/15
to cefs...@googlegroups.com
Hey Jorn,
I'm wondering if maybe we switch the `<` to `=` and include it as the 10th item?
If we had to remove something, then probably the JS alert one?
Alex
I'm wondering if maybe we switch the `<` to `=` and include it as the 10th item?
If we had to remove something, then probably the JS alert one?
Alex
Michael M
Aug 17, 2015, 12:07:56 AM8/17/15
to CefSharp
I've noticed that CefSharp has been upgraded to 3.2357.1287, but I'm still seeing the IME issue (also in the test builds).
Alex Maitland
Aug 17, 2015, 4:15:09 AM8/17/15
to CefSharp
If the problem is reproducable with the `cefclient` demo app using
--off-screen-rendering-enabled then the issue will need to be raised upstream.Message has been deleted
Angshuman
Jun 10, 2018, 5:36:02 AM6/10/18
to CefSharp
Hi,
How can implementing IWpfKeyboardHandler make IME inline for WPF ? Could you please provide some hints / guidance here ?
Reply all
Reply to author
Forward
0 new messages