Skip to content

Commit b3eceda

Browse files
thymikeeclaude
thymikee
and
claude
committed
fix(snapshot): stop sibling-sized chrome containers from covering their own region (#2996)
A chrome container published with exactly the frame of a sibling reports that sibling's footprint instead of a surface drawn over it, but the occlusion pass read its box as covering evidence. `isFullViewportChromeContainer` only exempts a container sized to the viewport root, so a container that stops short of it condemned content on both sides. Captured live on an iPhone 18 Pro (iOS 27.0) through the shipped publication path (`buildSnapshotState`): a system app's bottom-bar container matching the 812pt content branch beside it marked 36 of that branch's nodes plus the navigation bar listed beside it; a JS-tab app's tab-bar badge container matching the platter content view beside it marked all 13 tab-bar nodes. Both now mark 0 and 2 respectively, the two survivors genuinely under the tab bar, and the Android IME path is untouched because only the tabbar/toolbar/navigationbar kinds qualify. Co-Authored-By: Claude Opus 4.8 <[email protected]>
1 parent 8c0edab commit b3eceda

2 files changed

Lines changed: 648 additions & 6 deletions

File tree

0 commit comments

Comments
 (0)