pj/sanderling
1
0 Fork 0
mirror of https://github.com/priyanshujain/sanderling.git synced 2026-10-02 19:17:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(sidecar): record why the stale ime flag stays out of reach

Browse Source
This commit is contained in:
pj committed 2026-08-15 20:11:09 +05:30
1 parent 4bbab3ff4c
commit 7ea9e2e6de
1 file changed
+8
Download Patch File Download Diff File Expand all files Collapse all files
sidecar/src/main/kotlin/dev/sanderling/sidecar/DriverBackend.kt
+8
View File
@@ -790,6 +790,14 @@ internal fun typeChunks(
// The mInputShown guard is load-bearing rather than an optimisation: BACK is // The mInputShown guard is load-bearing rather than an optimisation: BACK is
// what closes an open IME, and BACK with no IME open navigates out of the // what closes an open IME, and BACK with no IME open navigates out of the
// screen, so an unguarded dismissal would make every InputText a back press. // screen, so an unguarded dismissal would make every InputText a back press.
//
// The flag trails the BACK it answers for, by about 0.6s on API 36, and a
// second dismissal inside that window reads the stale true and back-presses an
// IME that has already gone. What keeps that unreachable is the caller: one
// dismissal per inputText, and the runner focuses the field with a tap before
// every InputText, which raises the IME again long before this probe runs. A
// caller that dismissed twice in a row, or typed without focusing first, would
// lose that margin.
internal fun dismissSoftKeyboard(shell: (String) -> String) { internal fun dismissSoftKeyboard(shell: (String) -> String) {
if (!shell("dumpsys input_method").contains("mInputShown=true")) return if (!shell("dumpsys input_method").contains("mInputShown=true")) return
shell("input keyevent 4") shell("input keyevent 4")