Skip to content

docs(frame): clarify safe-area env injection - #9

Merged
lbb00 merged 1 commit into
mainfrom
docs/frame-safe-area-env
Sep 8, 2026
Merged

docs(frame): clarify safe-area env injection#9
lbb00 merged 1 commit into
mainfrom
docs/frame-safe-area-env

Conversation

@lbb00

@lbb00 lbb00 commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

safe-area-bottom and deviceProfile.safeAreaInsets.bottom update the frame's metrics, CSS custom properties and rendering, but they do not change the browser's native env(safe-area-inset-bottom) value. The previous documentation mentioned this limitation without showing which values do change or how separately hosted content should receive them.

The English and Chinese frame READMEs now document the boundary with a concrete bottom-inset example. They also explain that Electron/Chromium hosts can inject native env() values with Emulation.setSafeAreaInsetsOverride, while @devicekit/frame itself does not manage CDP sessions. The changelog records the clarification.

Verified with pnpm build, pnpm test (1,042 tests, 0 skipped), pnpm lint, pnpm check-types, and git diff --check.

@lbb00
lbb00 merged commit 0dd3b99 into main Sep 8, 2026
2 checks passed
@lbb00
lbb00 deleted the docs/frame-safe-area-env branch September 8, 2026 05:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant