Keep rail-collapsed: alive in Tailwind for scaffold.blade.php's one use
Plan step 36 follow-up. Deleting navigation.css also deleted the only definition of the rail-collapsed: custom variant, which scaffold.blade.php's data-app-shell-actions row still uses (rail-collapsed:flex-col) — scaffold's own rewrite is a later batch, so it is still Tailwind. Left alone, that class would silently stop matching anything. The definition moves into tailwind.css, updated to the data-md-* hooks navigation-rail.css now renders (data-rail and data-rail-auto are unchanged, so those branches needed nothing); otherwise it reproduces the same seven branches navigation-rail.css's own header documents, so the two cannot drift silently in what "collapsed" means. It goes with the scaffold's own rewrite. theme-script.blade.php's doc comment, which named the old variant, now points at navigation-rail.css directly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
cbd7d01c62
commit
20b062846d
@@ -28,7 +28,7 @@
|
||||
|
||||
The rail rides along for the theme's reason: <html data-rail> is `expanded` or `collapsed`
|
||||
(`livewire-material.rail.storage_key`, falling back to `rail.default`), and a collapsible
|
||||
rail's width is CSS keyed on it (the `rail-collapsed:` variant). Set any later, a collapsed
|
||||
rail's width is CSS keyed on it directly (resources/css/components/navigation-rail.css). Set any later, a collapsed
|
||||
rail would paint wide and snap shut on every load. `$store.rail` (resources/js/navigation.js)
|
||||
changes it. <html data-rail-auto> rides with it and says nothing was stored — the value is only
|
||||
`rail.default`, not a choice — so `<x-scaffold>`'s adaptive rail can start collapsed in the
|
||||
|
||||
Reference in New Issue
Block a user