Skip to content

Commit 43ecfec

Browse files
committed
docs(evidence): re-run the keyboard band at the z-order-only head
Same device, same choreography, same facts: visibility-only false on the settings home, visibility-only true with the IME raised, a bare in-band coordinate press dispatching under the fail-open guard, and one Back returning the fact to hidden. The rect-share rule sections are rewritten for the z-order-only producer; the landscape note no longer derives from rect geometry.
1 parent 8da093e commit 43ecfec

1 file changed

Lines changed: 19 additions & 17 deletions

File tree

‎docs/evidence/harmonyos-keyboard-band-2026-11-08.md‎

Lines changed: 19 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,15 @@
11
# HarmonyOS keyboard band fact, live, 2026-11-08 (fixed run 2026-11-09)
22

33
Evidence for #4285 (report the keyboard band in snapshot responses), re-run at the
4-
rebased head after the review found the published frame wrong. The window-manager
4+
z-order-only head after review asked for the frame branch to go. The window-manager
55
table on this build never carries the key plane: the panel row reports the whole
6-
display whether the keyboard shows or hides. The producer therefore publishes
7-
visibility, and publishes a band frame only when the table proves the rect covers
8-
under a 0.9 share of the display's area (`DISPLAY_SPANNING_RECT_SHARE`: at or above
9-
that share the panel is the window manager's full-surface container, not a key
10-
plane). This run shows that contract live, with the guard regressions
11-
the old full-screen frame caused now retired. Fix commit: `2878b86e4`.
6+
display whether the keyboard shows or hides. The producer therefore reads only the
7+
panel row's z-order and publishes visibility — it never publishes a frame, so the
8+
0.9-share threshold (`DISPLAY_SPANNING_RECT_SHARE`) and the largest-rect display
9+
derivation are gone: what they guarded against (a display-sized frame marking every
10+
on-screen point keyboard-covered) cannot be constructed any more. This run
11+
re-verifies the same facts at the new head. First fix: `2878b86e4`; simplification
12+
follows the review question of 2026-11-10.
1213

1314
## Device
1415

@@ -43,11 +44,13 @@ keys-only crop below starts at y 1600); the IME window surface covers the displa
4344
No public source reports that inner band: the window table carries window-surface
4445
rects, and `hidumper -s InputMethodService -a '-a'` lists installed IMEs
4546
(`小艺输入法`) with no geometry. A rect the table cannot prove smaller than the
46-
display is the container, not a band — publishing it as `visible` made the tap
47-
guard read every on-screen point as keyboard-covered (the `@e20` refusal in the
48-
previous revision of this file was that false refusal, presented as a feature).
47+
display is the container, not a band — publishing one as `visible` made the tap
48+
guard read every on-screen point as keyboard-covered (the `@e20` refusal in an
49+
earlier revision of this file was that false refusal, presented as a feature).
50+
The producer no longer reads the rect column at all: z-order decides visibility,
51+
and the fact is always `visibility-only`.
4952

50-
## The fact through a raise and a dismiss (branch CLI, head `2878b86e4`)
53+
## The fact through a raise and a dismiss (branch CLI, z-order-only head)
5154

5255
Settings home, keyboard hidden:
5356

@@ -107,10 +110,9 @@ later taps read.
107110
Not run. The device exposes no public rotation channel — `uitest` has no rotate
108111
subcommand, and agent-device's own `setHarmonyOrientation` answers
109112
UNSUPPORTED_OPERATION on HarmonyOS — so the landscape run needs a physical
110-
rotation this session cannot perform. The rect-share rule is
111-
orientation-independent: it compares the panel rect against the largest rect in
112-
the same table, whatever the display's aspect, and the real-row fixtures pin both
113-
states.
113+
rotation this session cannot perform. The producer is orientation-independent by
114+
construction: z-order does not depend on rotation, nothing derives from rect
115+
geometry, and the real-row fixtures pin both states.
114116

115117
## Landing order
116118

@@ -121,7 +123,7 @@ help conflict resolved.
121123
## Reproduce
122124

123125
```sh
124-
# head 2878b86e4, built in the PR worktree
126+
# z-order-only head, built in the PR worktree
125127
node bin/agent-device.mjs open com.huawei.hmos.settings --activity com.huawei.hmos.settings.MainAbility \
126128
--platform harmonyos --serial 77TYD26826028730
127129
node bin/agent-device.mjs snapshot --json --platform harmonyos --serial 77TYD26826028730 # visibility-only false
@@ -136,4 +138,4 @@ hidumper -s WindowManagerService -a -a # on the device: the raw rows quoted ab
136138
```
137139

138140
CI cannot exercise a HarmonyOS device; this file is the device-side proof of the
139-
parse, the rect-share rule, and the guard behavior.
141+
z-order parse, the visibility-only fact, and the guard behavior.

0 commit comments

Comments
 (0)