<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - kmfl keyboard entry jumps around to other textboxes or beginning of line in editeng" href="https://bugs.documentfoundation.org/show_bug.cgi?id=137620#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - kmfl keyboard entry jumps around to other textboxes or beginning of line in editeng" href="https://bugs.documentfoundation.org/show_bug.cgi?id=137620">bug 137620</a> from <a class="email" href="mailto:jluth@mail.com" title="Justin L <jluth@mail.com>"> Justin L</a> <pre>(In reply to Caolán McNamara from <a href="show_bug.cgi?id=137620#c4">comment #4</a>) > does KMFL directly use accessibility calls or does it use > "delete-surrounding" and "retrieve-surrounding" GTK-IM signals delete-surrounding. Here is a quote I found in my email: "KMFL (and other inputs methods) need to be able to delete text that has been previously entered. There are couple of ways to do this, one being to use a system call like "delete surrounding text". Another method is to simulate the backspace key. The former method is the preferred method because it gives better control over what is deleted. However applications have to be written to support "surrounding text". Apps are supposed to report to ibus whether they support "surrounding text" calls and if they don't, then kmfl falls back to simulating the backspace key.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>