Greg Pomerantz
a83cc1a72f
The boundary trace (PADIME at EditorStateChanged) showed why a desynchronized IME never heals itself: gioui's EditorReplace advances its stored selection state when the commit arrives, so the post-commit selection push is always deduplicated away and updateSelection is never sent after a commit. A desynced IME is therefore healed only by a snippet restart — and the resync was armed only after THREE consecutive anomalies, while the phone incident's first anomaly (a 5-rune autocorrect 19,000 runes from the caret, width > 2) sailed through the old <=2-rune guard and clobbered distant text before any resync could fire. Now: - the guard also snaps commits that are far from the caret AND outside the live selection (a legitimate commit is always local: at the caret, inside the selection, or a nearby correction); a distant commit lands at the caret instead of clobbering text; - the resync is armed on the FIRST anomalous commit (snapped or distant), not after a streak; the streak counter is gone; - imeSelectionRuneRange() lets the guard allow selection replacements anywhere. TestRealFile_IMEForceResync rewritten for the new semantics and extended with the distant-replacement case (must land at the caret and arm the resync).
20 lines
395 B
Modula-2
20 lines
395 B
Modula-2
module pad
|
|
|
|
go 1.24.2
|
|
|
|
require (
|
|
gioui.org v0.10.2
|
|
golang.org/x/image v0.26.0
|
|
golang.org/x/sys v0.39.0
|
|
)
|
|
|
|
require (
|
|
gioui.org/shader v1.0.9 // indirect
|
|
github.com/go-text/typesetting v0.3.4 // indirect
|
|
golang.org/x/exp/shiny v0.0.0-20250408133849-7e4ce0ab07d0 // indirect
|
|
golang.org/x/net v0.48.0 // indirect
|
|
golang.org/x/text v0.32.0 // indirect
|
|
)
|
|
|
|
replace gioui.org => /home/gmp/gioui
|