fix: make shared page bodies full width
This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
# Full-width shared page body
|
||||
|
||||
## What changed
|
||||
|
||||
`android/app/src/main/java/net/awan/pipelines/ui/components/DetailTabs.kt` no longer
|
||||
centres wide `DetailTabBody` content inside the artificial `DETAIL_MAX_WIDTH_DP` cap.
|
||||
The body now passes its page modifier through at the available safe-area width for
|
||||
Runs, Pipelines, Chats and Settings. Insets, scroll padding and narrower internal
|
||||
layouts (including chat bubbles) remain owned by their respective callers.
|
||||
|
||||
The wide navigation rail and pane-stack policy were not changed. The obsolete
|
||||
`DETAIL_MAX_WIDTH_DP` token was removed from `ui/theme/Dimens.kt`; no dependency or
|
||||
server change is involved.
|
||||
|
||||
`DetailTabsTest` pins the full-width body implementation and guards against restoring
|
||||
the centered cap. Device rendering on compact and wide windows remains for the UI
|
||||
review stage.
|
||||
|
||||
## Documentation now stale (for `docs-fold`)
|
||||
|
||||
- `android/README.md` near the detail-tabs geometry/token description still names
|
||||
`DETAIL_MAX_WIDTH_DP` as the wide page-body cap. Remove that token from the
|
||||
description and state that shared page bodies use the available safe-area width;
|
||||
keep any separate navigation-rail width description unchanged.
|
||||
Reference in New Issue
Block a user