mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-21 03:26:07 +00:00
fd35f79c36
TestFlight feedback: on an iPhone Duo the status capsule in the top right
corner covered the trip's controls, its day chips, the map's category bar and
the first cards of every trip tab, upright and on its side. The app has
measured the capsule since 0f42b8b8a, but only the shell's own bars and page
used it, and the trip, its map and the sheets place their own controls.
- Upright, a control row in the capsule's height stands beside it and the
content starts below it: the trip's top row and day chips, the map's
category bar, the road trip's stage bar, every trip tab's first row, the
places browser, the plan timeline, docked and card sheets, the assistant,
the account menu, the image viewer's close button, the atlas search,
vacay's header and a journey's content and map controls.
- On a wide window the page gives up the capsule's side over the whole
height instead, as an iPhone on its side does for its camera: lifting each
page below the capsule cost a quarter of the height of an unfolded Duo.
The list tabs, the assistant panel and the form sheets end before it too.
- Screens whose first row is part of the page (settings, administration,
collections) are lifted until that row is below the capsule; screens that
keep clear of it by themselves (atlas, vacay, a journey) are not lifted.
- Right to left the rail stands on the capsule's side and takes it.
All of it reads the corner variables the app publishes, which are 0 on every
other device and before iOS 26, so nothing else moves. The rules for the
screens that place their own controls live in mobile/corner.css.
32 lines
1.5 KiB
CSS
32 lines
1.5 KiB
CSS
/* ── An element in a top corner (an iPhone Duo's status capsule) ──────────────
|
|
Beside mobile.css, which holds the variables these read (--m-corner-*).
|
|
For the screens that place their own controls rather than sit in .m-page
|
|
(the trip, its map). Every variable is 0 without such an element, so these
|
|
change nothing on any other device.
|
|
m-corner-beside: a control row in the corner's height ends before it.
|
|
m-corner-side: a layer that fills the page ends before the corner's side on
|
|
a wide window (--m-corner-side-*, 0 upright, where content starts below the
|
|
corner through --m-corner-clear instead).
|
|
The element sits where the hardware puts it, whatever the reading
|
|
direction, so right to left swaps the two sides back. */
|
|
.m-corner-beside {
|
|
margin-inline: var(--m-corner-l-gap, 0px) var(--m-corner-r-gap, 0px);
|
|
}
|
|
html[dir='rtl'] .m-corner-beside {
|
|
margin-inline: var(--m-corner-r-gap, 0px) var(--m-corner-l-gap, 0px);
|
|
}
|
|
.m-corner-side {
|
|
margin-inline: var(--m-corner-side-l, 0px) var(--m-corner-side-r, 0px);
|
|
}
|
|
html[dir='rtl'] .m-corner-side {
|
|
margin-inline: var(--m-corner-side-r, 0px) var(--m-corner-side-l, 0px);
|
|
}
|
|
/* m-corner-beside-in: m-corner-beside for a row inside .m-page, upright only
|
|
(on a wide window the page itself already ends before the corner). */
|
|
.m-corner-beside-in {
|
|
margin-inline: var(--m-corner-in-l, 0px) var(--m-corner-in-r, 0px);
|
|
}
|
|
html[dir='rtl'] .m-corner-beside-in {
|
|
margin-inline: var(--m-corner-in-r, 0px) var(--m-corner-in-l, 0px);
|
|
}
|