/* Without a script there is nothing to toggle, so the CSS the design kit ships takes over: no burger, the bar as a static list, and the panels on hover and :focus-within. `:focus-within` is what makes it keyboard operable - the trigger itself is inside the group, so tabbing to it opens the panel and the links behind it become reachable. Written out rather than expressed in utilities: this block is left untouched by Astro (`is:inline`), so it is plain CSS. 1024px is `--breakpoint-lg`, which a media query cannot read from a variable. **`@layer base` and `!important` together are load-bearing, and neither works without the other.** The bar and the panels carry the `hidden` attribute in the markup, so that a drawer does not flash open on a phone in the moment between parse and hydration. Tailwind's preflight implements that attribute as `[hidden]:where(:not([hidden="until-found"])) { display: none !important }` - an important declaration, and one that sits inside `@layer base`. For *important* declarations the cascade reverses the layer order: an important declaration in a layer beats an important declaration in no layer at all, whatever its specificity. So an unlayered `display: flex !important` here loses to preflight, and losing it means a JavaScript-less visitor gets a header with no navigation in it at all. Declaring these rules into `base` puts them in the same layer as preflight, where specificity decides again and `[data-mega-menu] [data-menu-bar]` (0,2,0) beats `[hidden]` (0,1,0). These rules are inside `<noscript>`, so they only ever apply where there is no script to remove the attribute. */ @layer base { [data-mega-menu] [data-menu-toggle], [data-mega-menu] [data-menu-close] { display: none; } [data-mega-menu] [data-menu-bar] { display: flex !important; } [data-mega-menu] [data-menu-group]:hover [data-menu-panel], [data-mega-menu] [data-menu-group]:focus-within [data-menu-panel] { display: block !important; } @media (max-width: 1023.98px) { [data-mega-menu] [data-menu-bar] { display: block !important; position: static; overflow: visible; padding: 0; background: transparent; } } }

12. Oktober 2020 · Kurse

Robocup-Seminar: Entwicklung eines Roboters mit Arduino

Das „Robocup-Seminar - Entwicklung eines Roboters mit Arduino“, startet am Donnerstag, 15. Oktober 2020 von 18.15 – 20.15 Uhr und richtet sich an Schülerinnen ab 13 Jahren, die bereits…

Ein Jugendlicher setzt seinen Lego-Roboter auf das grüne Spielfeld, gegenüber wartet der zweite Roboter beim Roboterfußball

Das „Robocup-Seminar - Entwicklung eines Roboters mit Arduino“, startet am Donnerstag, 15. Oktober 2020 von 18.15 – 20.15 Uhr und richtet sich an Schüler*innen ab 13 Jahren, die bereits fortgeschrittene Programmiererfahrungen haben. Es gibt noch wenige freie Plätze: Kursportal

Zurück zu allen Beiträgen