diff --git a/resources/css/components/menu.css b/resources/css/components/menu.css index 172f6672..65e1bd56 100644 --- a/resources/css/components/menu.css +++ b/resources/css/components/menu.css @@ -2,7 +2,7 @@ * The menus: `` and what a form's own dropdowns wear too, so a menu and a form read as * one family. * - * Two lists wear the dropdown: + * Three lists wear it: * * - ``'s own popover (`[data-md-menu-popover]`) and, inside it, a submenu * (`[data-md-submenu]`, menu-item.css). @@ -19,7 +19,7 @@ * focus. * * `[data-md-menu]` is ``'s root, holding the trigger and the popover; the popover itself - * is `[data-md-menu-popover]`, capped at 18rem so a long menu scrolls instead of running off the + * is `[data-md-menu-popover]`, capped at 288px so a long menu scrolls instead of running off the * top layer's edge (ACT-04), and transitions in by growing from its trigger's corner while it * fades, on the spatial and effects springs respectively (ACT-26). `data-md-vibrant` swaps its * container for tertiary-container; a nested submenu inherits the colour through diff --git a/resources/views/components/menu.blade.php b/resources/views/components/menu.blade.php index b0a7f573..f736e478 100644 --- a/resources/views/components/menu.blade.php +++ b/resources/views/components/menu.blade.php @@ -33,7 +33,7 @@ same key. A menu too long for the window scrolls, as M3 asks, rather than running off the edge of the - top layer where nothing can reach it (ACT-04): 18rem at most, and less on a short window. The + top layer where nothing can reach it (ACT-04): 288px at most, and less on a short window. The arrow keys, Home, End and typeahead bring the item they move to into view, and a disabled item is among them: M3 keeps one reachable so a person can find out that it exists.