mirror of
https://github.com/pewdiepie-archdaemon/odysseus.git
synced 2026-06-17 18:25:26 -04:00
Email reader: grow header min-height to fit wrapped 2-row cluster
When the cluster wraps to 2 rows (44 + 4 gap + 44 = 92px tall), it was peeking out below the header bottom because min-height stayed at 60px (only ~44px of cluster room). Bumped min-height to 108px inside the same <600 container query so the wrapped cluster sits fully inside the header with 8px breathing room top + bottom.
This commit is contained in:
+8
-1
@@ -10530,7 +10530,7 @@ textarea.memory-add-input {
|
|||||||
Matches the .memory-desc treatment (same color + 11px size) so it
|
Matches the .memory-desc treatment (same color + 11px size) so it
|
||||||
visually belongs to the section description, not the switch. */
|
visually belongs to the section description, not the switch. */
|
||||||
.admin-toggle-state {
|
.admin-toggle-state {
|
||||||
font-size: 11px;
|
font-size: 10px;
|
||||||
line-height: 1.5;
|
line-height: 1.5;
|
||||||
font-weight: normal;
|
font-weight: normal;
|
||||||
letter-spacing: 0.02em;
|
letter-spacing: 0.02em;
|
||||||
@@ -28291,6 +28291,13 @@ button .spinner-whirlpool {
|
|||||||
.email-reader-meta > .email-reader-meta-details {
|
.email-reader-meta > .email-reader-meta-details {
|
||||||
padding-right: 170px;
|
padding-right: 170px;
|
||||||
}
|
}
|
||||||
|
/* Cluster wrapped to 2 rows (44px + 4 gap + 44px = 92px) sits
|
||||||
|
absolute above the From baseline. Grow the header so its bottom
|
||||||
|
fully contains the cluster instead of letting it peek out.
|
||||||
|
8px top padding + 92px cluster + 8px breathing = ~108. */
|
||||||
|
.email-reader-header {
|
||||||
|
min-height: 108px;
|
||||||
|
}
|
||||||
}
|
}
|
||||||
/* Very narrow reader: once the chip span has shrunk to its ~4
|
/* Very narrow reader: once the chip span has shrunk to its ~4
|
||||||
character min, the cluster snaps to absolute overlay with a soft
|
character min, the cluster snaps to absolute overlay with a soft
|
||||||
|
|||||||
Reference in New Issue
Block a user