dandri/simplex-chat
1
0
Fork 0
mirror of https://github.com/simplex-chat/simplex-chat.git synced 2026-07-29 12:00:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

plans: correct recomposition count and note commit subject scoping

Browse Source
This commit is contained in:
Narasimha-sc
2026-07-15 10:15:26 +00:00
parent 60060d28a7
commit e375962ed7
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plans/2026-07-13-fix-command-hover-cursor.md
+5 -3
View File
@@ -110,15 +110,17 @@ hover.
`setCursor` call fires only when the cursor type actually changes. The canvas component lookup
(recursive tree walk) runs once per window and is cached, including negative results (a miss is
unreachable in practice — pointer events originate from the rendered canvas — kept as a guard).
- One added recomposition when the pointer exits text that showed a Hand (the exit reset writes
`icon.value` Hand→Text); otherwise the icon state logic is unchanged. Android is a no-op.
- Up to two added recompositions per exit/re-enter cycle of a Hand region (the exit reset writes
`icon.value` Hand→Text, making the next re-enter a Text→Hand write where pre-fix both were
no-ops); otherwise the icon state logic is unchanged. Android is a no-op.
Framework line numbers cited above are from the official `ui-desktop-1.8.2`/`foundation-desktop-1.8.2`
sources jars on Maven Central; they will drift on upgrade.
## Testing
Verified on Linux (AppImage), in two stages:
Verified on Linux (AppImage), in two stages (commit subjects name the defect layer each commit
fixes; the user-visible symptom needed both layers, per stage 1 below):
1. A build with only the detection-layer fix (lossless `detectCursorMove`) was tested first and
the stale-cursor symptom **still reproduced** — this is the empirical justification for the