Repository navigation
Commit b7fdd71
committed
fix(contracts): dock the keyboard band to the bottom edge, not the midline
Band eligibility asked whether the topmost keyboard rect sat in the lower half of the
viewport — a height claim dressed as a docking claim. Measured on iPhone 17 Pro
(iOS 26.2) with Safari raising the system keyboard, portrait reports the key plane at
583..816 of an 874 pt viewport and landscape at 75..402 of a 402 pt one. The landscape
keyboard therefore starts above that orientation's midline at 201, so the old rule
declined to measure it and the guard was silently off in landscape: the same silent
misfire #2589 reports, in the second orientation.
Eligibility is now the measured question. Keyboard geometry has to come within 80 pt of
the viewport's bottom edge to own the band down to it. Portrait's 58 pt home-indicator
strip passes with 22 pt of slack, landscape passes exactly on the edge, and a surface
that stops further up — an iPad floating or split keyboard, which the height heuristic
could also misread as a system band — leaves the band unmeasured so the tap fails open
rather than refusing on geometry that says nothing about the bottom of the screen.
Docking cannot be read off height, which is what the golden table now pins: the same
keyboard is 233 pt of an 874 pt viewport in portrait and 327 pt of a 402 pt one in
landscape. Six cases gained the docked bottom row a real tree reports beside its top
row, and five new cases pin docking itself plus the boundary it accepts: a
bottom-anchored app keypad wearing the keyboard types owns its band.
`resolveVisibleKeyboardSurface` is module-private. The table derives its band through
`expected.frame`, so nothing outside the module needed it, and the surface derivation
assertions that only that file could see now live in the table.1 parent 128cab9 commit b7fdd71
3 files changed
Lines changed: 1247 additions & 171 deletions
File tree
- contracts/fixtures
- packages/contracts/src
0 commit comments