Using Konqueror with KHTML engine, choose input method fcitx to type CJK character into the webpage, the word-selecting window will not appear at the correct place where I am typing ( when kimpanel is not used ) , or won't appear at all ( when package kdeplasma-addons-applets-kimpanel is installed and used ). ====Chinese translation:===== KDE 下使用 Konqueror 与 KHTML 时，使用 fcitx 作为输入法，在不使用 Kimpanel，即使用经典 UI 时，光标跟随位置不正常（可能靠下几百个像素）。在使用 Kimpanel 时，只会在显示带有下划线的候选词，但根本没有候选框。 ========================== Relavant discussion can be found here: http://code.google.com/p/fcitx/issues/detail?id=569 https://groups.google.com/forum/#!msg/fcitx-notifications/AwyXFZV7E7g/DPayjPvX_c4J The discussion result is that it should be a bug of Konqueror rather than fcitx. Reproducible: Always Steps to Reproduce: 1.Install konqueror, fcitx, fcitx-libpinyin (and kdeplasma-addons-applets-kimpanel , actually the behaviour will change if kimpanel is used.) 2.use KHTML engine, find a place to type, activate the input method using ctrl+space. 3.start typing. Actual Results: * When kimpanel is not used, the windows shown for you to select characters will not follow the cursor. Maybe it is several hundreds pixels below the correct place. * When kimpanel is used and added as a plasma widget, NO word-selecting window will show up. Expected Results: * No matter kimpanel is used or not, the word-selecting window will show up beside the cursor. * As described in https://fcitx-im.org/wiki/Fcitx , Kimpanel and the classic-UI are two different UI of fcitx. Kimpanel is a DBus-based User Interface for Fcitx while classic-UI a is a Xlib-based user interface. Both of them are not working well with Konqueror+KHTML. * If I choose the Webkit engine for Konqueror, there won't be any problem at all. * Typing in search bar and address bar works normally. * Using Archlinux, updated on 1th Jun. 2014 P.S. This bug should have existed for years.
> find a place to type But where? You say that both search and address bar work normally.
(In reply to Christoph Feck from comment #1) > > find a place to type > > But where? You say that both search and address bar work normally. Sorry, it should be "find a place within the webpage that can type words", or any kind of textbox within the webpage. For example, open https://www.google.com and type words in the searching *textbox* of google.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!