200
edits
Mobile/IME: Difference between revisions
Added Debugging IME section
AlexPakhotin (talk | contribs) |
AlexPakhotin (talk | contribs) (Added Debugging IME section) |
||
| Line 35: | Line 35: | ||
As most of the external IME events handling is done by the BaseInputConnection class, Gecko composition state is a bit artificial, and sometimes may not exactly correspond to the state in BaseInputConnection class. There are areas for improvements here. | As most of the external IME events handling is done by the BaseInputConnection class, Gecko composition state is a bit artificial, and sometimes may not exactly correspond to the state in BaseInputConnection class. There are areas for improvements here. | ||
= Debugging IME = | |||
Due to the asynchronous nature of IME interaction the best way to debug the issues is to read and try to understand the extended logs. | |||
There is a DEBUG flag in the GeckoInputConnection class, which enables debug log output. GeckoInputConnection.java also contains a special subclass DebugGeckoInputConnection, which is enabled by the same flag, and writes additional logs on each IME-related method call. | |||
widget/android/nsWindow.cpp also writes additional IME-related logs when DEBUG_ANDROID_IME flag is defined. | |||
= Bugs = | = Bugs = | ||