loopable / web /src /styles /wave53 /sheet-rail.css
fsanyoto's picture
Deploy AIOS web (React glide grid + FastAPI slice)
792ee39 verified
Raw History Blame Contribute Delete
3.96 kB
/* ---------------------------------------------------------------------------
styles/wave53/sheet-rail.css - the LAST pixel of Sheet/Data rail parity
(wave 53, W53-T04, owner instruction 15, the owner's THIRD report).
⭐⭐ THE MEASUREMENT, NOT THE DIFF. Two 1440x900 frames were taken at `#/sheet` and at
`#/data?database=customer_data` and scanned for dark-pixel row bands in the rail column
(x = 300..560). W51-T09 and W52-T21 had already closed most of the gap; what remained was
exactly one pixel, and it was in the PATH ROW, not in the create door:
band Sheet Data
.cg-views-top icons 61-70 61-70 <- agree
rule under .cg-views-top 87 87 <- agree
path row text 103-112 104-113 <- 1px
rule under the path row 123 124 <- 1px
"+ Create new..." 145-154 146-155 <- 1px
"Find..." 173-182 174-183 <- 1px
Everything from the path row DOWN sat one pixel HIGH on the Sheet. The white space the
instruction describes is therefore not above "+ Create new..." at all; it is the path row
above it being one pixel SHORT, which pulls the whole stack up.
⭐⭐ WHY THE ROW IS SHORT, AND WHY THERE IS NO MAGIC NUMBER BELOW. Both rails render the same
element, `nav.cg-fold-head.cg-view-path.cg-segmented-path`, and it is `box-sizing: border-box`
everywhere (index.css:42). Its own chrome is identical on both:
.cg-fold-head padding: 1px 2px (index.css:5875)
.cg-view-path border-bottom: 1px (wave46/rail-select.css:245 for Data,
wave52/parity.css for Sheet)
.cg-segmented-path min-height: 30px (same two sheets)
What is NOT identical is the tallest CHILD, and that is correct rather than a defect. The
Data rail's row ends in `databaseActions`, a 28px `button.shell-dots`
(`ViewSidebar.tsx:2718`, sized by `wave46/rail-select.css:202`). The Sheet rail has no
database to act on, so wave-49 R2 requires that control to be ABSENT rather than
present-and-inert, and the row's tallest child is a 26px `.cg-path-history-button`
(index.css:557).
So the two rows resolve their heights by DIFFERENT rules:
Data 28 + 1 + 1 + 1 = 31px natural, which OVERFLOWS the 30px floor and wins
Sheet 26 + 1 + 1 + 1 = 29px natural, which is under the floor, so 30px wins
The shared `min-height: 30px` was never the Data row's height. It is a floor the Data row
clears by one pixel and the Sheet row does not reach. The honest fix is therefore not to
invent a 28px control the Sheet cannot honour, and not to nudge a margin: it is to seat the
Sheet's path row in the same 31px box the Data row COMPUTES, and to say where each of those
four pixels comes from.
⛔ SPECIFICITY IS DELIBERATE AND MUST NOT BE "SIMPLIFIED". `wave52/parity.css` states
`.sheet-page .cg-segmented-path` at (0,2,0). A tie here would leave the winner to whichever
sheet the bundler emits last, which no lane controls and which can flip between builds - the
same coin flip `wave46/rail-select.css` warns about at its `button.shell-dots` rule. Adding
`.cg-view-path` makes this (0,3,0) and it wins outright.
⛔ SCOPED UNDER `.sheet-page` so it can never reach the Data rail, which has no `.sheet-page`
ancestor. This lane owns the Sheet side only.
⛔ TOKENS ONLY: no colour, no font-size, no z-index is declared here at all.
--------------------------------------------------------------------------- */
.sheet-page .cg-view-path.cg-segmented-path {
/* 28px (the height the Data row's `button.shell-dots` gives it)
+ 1px + 1px (`.cg-fold-head`'s vertical padding)
+ 1px (`.cg-view-path`'s bottom rule)
= the 31px border box the Data rail's path row measures. */
min-height: 31px;
}