Fix SarahUI styling: cascade layer order and the missing basecoat structure All eight SarahUI button variants rendered identically on staging. Two independent causes, both from the Step 6 port: 1. Cascade layers. DaisyUI emits into its own `daisyui` layer, and in the deployed bundle that layer is first declared at byte 37569 while `components` is declared at 10838. A later-declared layer wins over an earlier one REGARDLESS of specificity, so DaisyUI's flat `.btn` beat every `.btn[data-variant=...]` rule in sarah.css. The rules were in the bundle all along (61 occurrences) and simply lost the cascade. Fixed by declaring the order explicitly, placed before the tailwindcss import so it is the first multi-name @layer statement -- only the first one establishes order; later statements can add names but cannot reorder. 2. Missing structure. Sarah imports 13 basecoat component stylesheets; this repo imported only base/base.css. sarah.css's `.btn` deliberately sets just gap, border, radius, colour, font, and transition -- display, padding, min-height, and background come from basecoat's button.css. So even with the cascade fixed, SarahUI controls would inherit DaisyUI's geometry. Imported the same 13 Sarah does, carrying its warning never to import basecoat.css/basecoat-base.css/basecoat-components.css. Consequence worth knowing: sarah.css now wins the `.btn` base for DaisyUI-classed buttons too (roughly 19 usages of `btn btn-primary`, `btn btn-ghost` and similar). Their `btn-*` modifiers still apply from the daisyui layer, but base geometry is now Sarah's. That is the `.btn` collision inherent to running two component systems, which UI-003 records as a transitional exception under the owner's basecoat decision. CSS-only change; no test behaviour is affected.
Fix SarahUI styling: cascade layer order and the missing basecoat structure
Deploy story
What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.
Not deployed through the forge lane
No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.
Changed files
-
modified
assets/css/app.css
Diff
1 file changed, +38 -0
assets/css/app.css modified +38
@@ -1,9 +1,47 @@
| 1 | 1 |
|
| 2 | 2 |
|
| 3 | 3 |
|
| 4 |
|
|
| 5 |
|
|
| 6 |
|
|
| 7 |
|
|
| 8 |
|
|
| 9 |
|
|
| 10 |
|
|
| 11 |
|
|
| 12 |
|
|
| 13 |
|
|
| 14 |
|
|
| 15 |
|
|
| 16 |
|
|
| 4 | 17 |
|
| 5 | 18 |
|
| 19 |
|
|
| 20 |
|
|
| 21 |
|
|
| 22 |
|
|
| 23 |
|
|
| 24 |
|
|
| 25 |
|
|
| 26 |
|
|
| 27 |
|
|
| 28 |
|
|
| 6 | 29 |
|
| 30 |
|
|
| 31 |
|
|
| 32 |
|
|
| 33 |
|
|
| 34 |
|
|
| 35 |
|
|
| 36 |
|
|
| 37 |
|
|
| 38 |
|
|
| 39 |
|
|
| 40 |
|
|
| 41 |
|
|
| 42 |
|
|
| 43 |
|
|
| 44 |
|
|
| 7 | 45 |
|
| 8 | 46 |
|
| 9 | 47 |
|