/**
 * Kata mobile menu.
 *
 * Figma: "menu mobile" and "menu mobile open", both on a 395 frame.
 *
 * This styles CORE'S navigation overlay rather than replacing it. The block
 * already ships the open and close buttons, the focus trap, the scroll lock,
 * Escape-to-close, and — with `openSubmenusOnClick` — submenu parents that are
 * real buttons carrying `aria-expanded`. All of that is easy to reimplement
 * badly, so none of it is reimplemented here; only the appearance is.
 *
 * Everything below is scoped to the open overlay at mobile widths, so the wide
 * navigation is untouched.
 */

:root {
	--kata-menu-icon-projects: url( "data:image/svg+xml,%3Csvg preserveAspectRatio=%22none%22 overflow=%22visible%22 style=%22display: block;%22 width=%2223.9911%22 height=%2223.9911%22 viewBox=%220 0 23.9911 23.9911%22 fill=%22none%22 xmlns=%22http://www.w3.org/2000/svg%22%3E %3Cg id=%22home-heart 1%22 clip-path=%22url(%23clip0_0_12)%22%3E %3Cpath id=%22Vector 604%22 d=%22M12.0003 11.3381L10.3235 10.2201L8.48668 10.7791L7.52832 12.7756L12.0003 18.4457L15.2745 16.3693L16.6321 12.7756L15.8335 10.2201H13.6774L12.0003 11.3381Z%22 fill=%22%23F049B4%22/%3E %3Cpath id=%22Vector%22 d=%22M12.1315 19.0957C11.6197 19.0957 11.1089 18.9247 10.682 18.5829C9.28154 17.4613 6.63253 14.7313 6.63253 12.4262C6.63253 10.5349 8.08999 8.99745 9.88132 8.99745C10.771 8.99745 11.5557 9.31533 12.1305 9.84913C12.7053 9.31633 13.49 8.99745 14.3796 8.99745C16.171 8.99745 17.6284 10.5359 17.6284 12.4262C17.6284 14.7323 14.9804 17.4623 13.5799 18.5839C13.1531 18.9257 12.6423 19.0957 12.1315 19.0957ZM9.88132 10.9957C9.19258 10.9957 8.63179 11.6375 8.63179 12.4252C8.63179 13.7007 10.5481 15.9139 11.9316 17.0215C12.0495 17.1184 12.2105 17.1184 12.3304 17.0215C13.7139 15.9139 15.6292 13.7007 15.6292 12.4242C15.6292 11.6355 15.0684 10.9947 14.3796 10.9947C13.7579 10.9947 13.1301 11.3686 13.1301 12.2033C13.1301 12.755 12.6833 13.2029 12.1305 13.2029C11.5777 13.2029 11.1309 12.755 11.1309 12.2033C11.1309 11.3106 10.4571 10.9947 9.88132 10.9947V10.9957ZM18.9929 23.9909H4.99814C2.24217 23.9909 0 21.7487 0 18.9927V9.72018C0 8.05679 0.822694 6.50837 2.20218 5.57672L9.19957 0.854477C10.8969 -0.291097 13.0931 -0.292096 14.7925 0.854477L21.7899 5.57572C23.1684 6.50637 23.9911 8.0548 23.9911 9.71918V18.9917C23.9911 21.7477 21.7489 23.9909 18.9929 23.9909ZM11.9965 1.99705C11.4118 1.99705 10.828 2.16899 10.3182 2.51286L3.32076 7.2341C2.49307 7.79289 1.99926 8.72155 1.99926 9.72018V18.9927C1.99926 20.6461 3.34475 21.9916 4.99814 21.9916H18.9929C20.6463 21.9916 21.9918 20.6461 21.9918 18.9927V9.72018C21.9918 8.72155 21.498 7.79189 20.6713 7.2341L13.6739 2.51286C13.1641 2.16899 12.5803 1.99705 11.9965 1.99705Z%22 fill=%22white%22/%3E %3C/g%3E %3Cdefs%3E %3CclipPath id=%22clip0_0_12%22%3E %3Crect width=%2223.9911%22 height=%2223.9911%22 fill=%22white%22/%3E %3C/clipPath%3E %3C/defs%3E %3C/svg%3E" );
	--kata-menu-icon-income: url( "data:image/svg+xml,%3Csvg preserveAspectRatio=%22none%22 overflow=%22visible%22 style=%22display: block;%22 width=%2224%22 height=%2224%22 viewBox=%220 0 24 24%22 fill=%22none%22 xmlns=%22http://www.w3.org/2000/svg%22%3E %3Cg id=%22city 1%22 clip-path=%22url(%23clip0_0_8)%22%3E %3Cpath id=%22Vector 605%22 d=%22M11.2324 8.58691L6.24463 3.66724L1.05145 8.04037V22.6628H11.2324V8.58691Z%22 fill=%22%239BE4FD%22/%3E %3Cpath id=%22Vector%22 d=%22M14 13H16V15H14V13ZM18 15H20V13H18V15ZM14 19H16V17H14V19ZM18 19H20V17H18V19ZM14 7H16V5H14V7ZM18 7H20V5H18V7ZM14 11H16V9H14V11ZM18 11H20V9H18V11ZM24 3V24H0V8.829C0 8.028 0.312 7.274 0.879 6.707L3.586 4C4.875 2.71 7.125 2.71 8.414 4L10 5.586V3C10 1.346 11.346 0 13 0H21C22.654 0 24 1.346 24 3ZM10 8.829C10 8.562 9.896 8.31 9.707 8.121L7 5.414C6.474 4.888 5.526 4.888 5 5.414L2.293 8.121C2.104 8.31 2 8.561 2 8.829V22H10V8.829ZM22 3C22 2.449 21.551 2 21 2H13C12.449 2 12 2.449 12 3V22H22V3ZM5 15H7V13H5V15ZM5 11H7V9H5V11ZM5 19H7V17H5V19Z%22 fill=%22white%22/%3E %3C/g%3E %3Cdefs%3E %3CclipPath id=%22clip0_0_8%22%3E %3Crect width=%2224%22 height=%2224%22 fill=%22white%22/%3E %3C/clipPath%3E %3C/defs%3E %3C/svg%3E" );
	--kata-menu-icon-urban: url( "data:image/svg+xml,%3Csvg preserveAspectRatio=%22none%22 overflow=%22visible%22 style=%22display: block;%22 width=%2224.0155%22 height=%2224.0155%22 viewBox=%220 0 24.0155 24.0155%22 fill=%22none%22 xmlns=%22http://www.w3.org/2000/svg%22%3E %3Cg id=%22flooding 1%22 clip-path=%22url(%23clip0_0_18)%22%3E %3Cpath id=%22Vector 606%22 d=%22M8.68283 5.13807C9.50331 5.50273 11.1167 6.83362 11.0071 9.24032C10.5968 9.51386 9.55766 10.1703 8.68283 10.6079C7.5893 11.1549 7.58842 11.9754 6.63142 13.8899C1.43528 16.7615 0.614344 11.8387 2.05055 9.65071C-0.342514 8.14649 1.70869 6.16367 3.28134 5.13807C2.32411 4.18085 3.00764 1.30906 6.63142 1.10394C9.53045 0.939844 9.20696 3.72499 8.68283 5.13807Z%22 fill=%22%23C4FF43%22/%3E %3Cpath id=%22Vector%22 d=%22M24.0245 22.6466C23.265 23.5171 22.1683 24.0155 21.0135 24.0155C19.8118 24.0155 18.7461 23.4731 18.0116 22.6326C17.2771 23.4731 16.2114 24.0155 15.0097 24.0155C13.8079 24.0155 12.7422 23.4731 12.0077 22.6326C11.2733 23.4731 10.2066 24.0155 9.0058 24.0155C7.80503 24.0155 6.73834 23.4731 6.00387 22.6326C5.2694 23.4731 4.20271 24.0155 3.00194 24.0155C1.8492 24.0155 0.751489 23.5161 -0.009 22.6466L1.49797 21.3297C1.87821 21.765 2.42657 22.0142 3.00194 22.0142C4.10565 22.0142 5.00323 21.1166 5.00323 20.0129H7.00451C7.00451 21.1166 7.90209 22.0142 9.0058 22.0142C10.1095 22.0142 11.0071 21.1166 11.0071 20.0129H13.0084C13.0084 21.1166 13.906 22.0142 15.0097 22.0142C16.1134 22.0142 17.011 21.1166 17.011 20.0129H19.0122C19.0122 21.1166 19.9098 22.0142 21.0135 22.0142C21.5889 22.0142 22.1373 21.765 22.5175 21.3297L24.0245 22.6466ZM5.79572e-06 12.0077C5.79572e-06 11.3023 0.190128 10.6138 0.545357 10.0064C0.190128 9.39905 5.79572e-06 8.71061 5.79572e-06 8.00515C5.79572e-06 6.54621 0.802522 5.22836 2.03732 4.53092C2.0133 4.3558 2.00129 4.17869 2.00129 4.00258C2.00129 1.79516 3.79645 0 6.00387 0C8.21129 0 10.0064 1.79516 10.0064 4.00258C10.0064 4.17969 9.99444 4.3558 9.97042 4.53092C10.7759 4.98521 11.3923 5.70767 11.7276 6.55822L13.2325 5.38046C14.2782 4.56194 15.7401 4.56194 16.7878 5.38046L23.0729 10.2996C23.6722 10.7679 24.0155 11.4724 24.0155 12.2339V18.0116H22.0142V12.2339C22.0142 12.0948 21.9491 11.9617 21.8401 11.8766L15.554 6.95648C15.2338 6.70632 14.7865 6.70532 14.4653 6.95648L8.34338 11.7476C8.12824 11.9157 8.00516 12.1688 8.00516 12.443V18.0116H6.00387V15.4539C5.41249 15.7992 4.73505 16.0103 4.00258 16.0103C1.79516 16.0103 5.79572e-06 14.2151 5.79572e-06 12.0077ZM3.12602 10.0064L2.52363 10.6759C2.28548 10.941 2.00229 11.3863 2.00229 12.0077C2.00229 13.1114 2.89987 14.009 4.00358 14.009C5.10729 14.009 6.0539 13.1114 6.0539 12.0077C6.16297 11.2863 6.5252 10.6298 7.11158 10.1715L9.99944 7.91109C9.95841 7.05654 9.36703 6.31306 8.52549 6.08492L7.43979 5.79073L7.85806 4.74705C7.95613 4.5019 8.00616 4.25174 8.00616 4.00258C8.00616 2.89887 7.10858 2.00129 6.00487 2.00129C4.90116 2.00129 4.00358 2.89887 4.00358 4.00258C4.00358 4.25174 4.05361 4.5019 4.15168 4.74705L4.56995 5.79073L3.48425 6.08492C2.61169 6.32107 2.00229 7.11058 2.00229 8.00515C2.00229 8.62655 2.28648 9.07184 2.52363 9.33701L3.12602 10.0064ZM12.0077 12.0077H18.0116V18.0116H12.0077V12.0077ZM14.009 16.0103H16.0103V14.009H14.009V16.0103Z%22 fill=%22white%22/%3E %3C/g%3E %3Cdefs%3E %3CclipPath id=%22clip0_0_18%22%3E %3Crect width=%2224.0155%22 height=%2224.0155%22 fill=%22white%22/%3E %3C/clipPath%3E %3C/defs%3E %3C/svg%3E" );
	--kata-menu-icon-development: url( "data:image/svg+xml,%3Csvg preserveAspectRatio=%22none%22 overflow=%22visible%22 style=%22display: block;%22 width=%2223.9998%22 height=%2224%22 viewBox=%220 0 23.9998 24%22 fill=%22none%22 xmlns=%22http://www.w3.org/2000/svg%22%3E %3Cg id=%22build-alt (1) 1%22 clip-path=%22url(%23clip0_0_15)%22%3E %3Crect id=%22Rectangle 5696%22 x=%2214.1471%22 y=%221.34824%22 width=%228.42814%22 height=%225.42993%22 fill=%22%23FFB657%22/%3E %3Cpath id=%22Vector%22 d=%22M19.4998 0H14.9999C13.8969 0 12.9999 0.897 12.9999 2V6C12.9999 7.103 13.8969 8 14.9999 8H21.9998C23.1028 8 23.9998 7.103 23.9998 6V4.5C23.9998 2.019 21.9808 0 19.4998 0ZM14.9999 6V2H19.4998C20.8788 2 21.9998 3.122 21.9998 4.5V6H14.9999ZM21.9998 10H7.99992V6C7.99992 4.897 7.10293 4 5.99994 4H4.49996C2.01898 4 0 6.019 0 8.5V19.5C0 21.981 2.01898 24 4.49996 24H19.4998C21.9808 24 23.9998 21.981 23.9998 19.5V12C23.9998 10.897 23.1028 10 21.9998 10ZM21.9998 16H12.9999V12H21.9998V16ZM15.9998 18V22H7.99992V18H15.9998ZM1.99998 8.5C1.99998 7.122 3.12097 6 4.49996 6H5.99994V10H1.99998V8.5ZM10.9999 12V16H1.99998V12H10.9999ZM1.99998 19.5V18H5.99994V22H4.49996C3.12097 22 1.99998 20.878 1.99998 19.5ZM19.4998 22H17.9998V18H21.9998V19.5C21.9998 20.878 20.8788 22 19.4998 22Z%22 fill=%22white%22/%3E %3C/g%3E %3Cdefs%3E %3CclipPath id=%22clip0_0_15%22%3E %3Crect width=%2223.9998%22 height=%2224%22 fill=%22white%22/%3E %3C/clipPath%3E %3C/defs%3E %3C/svg%3E" );
	--kata-menu-icon-construction: url( "data:image/svg+xml,%3Csvg preserveAspectRatio=%22none%22 overflow=%22visible%22 style=%22display: block;%22 width=%2224.0299%22 height=%2224.0299%22 viewBox=%220 0 24.0299 24.0299%22 fill=%22none%22 xmlns=%22http://www.w3.org/2000/svg%22%3E %3Cg id=%22crane 1%22 clip-path=%22url(%23clip0_0_4)%22%3E %3Cpath id=%22Vector 607%22 d=%22M6.96412 0.867622C4.34055 0.40471 1.40872 4.57126 1.17715 6.11437C0.763678 7.17792 1.98229 7.27775 2.64328 7.19471C3.81618 7.62681 16.6607 6.65453 22.9364 6.11437C18.4868 4.51976 9.06298 1.23795 6.96412 0.867622Z%22 fill=%22%23F0553D%22/%3E %3Cpath id=%22Vector%22 d=%22M22.4479 16.3763C22.1926 16.2382 22.0274 15.9178 22.0274 15.5583V8.00895C23.0286 8.00895 23.8016 7.54037 23.9898 6.62323C24.166 5.80821 23.7575 4.99821 22.9976 4.65478C22.9635 4.63876 10.3138 0.534663 10.3138 0.534663C7.4072 -0.454566 4.91511 -0.0690874 2.89059 1.70111L0.867077 3.57644C0.0660821 4.27631 -0.20926 5.37267 0.165205 6.36991C0.538669 7.36615 1.46882 8.00895 2.53215 8.00895H4.00498V22.0264H1.00124C0.447556 22.0264 0 22.4749 0 23.0276C0 23.5803 0.447556 24.0288 1.00124 24.0288H14.0174C14.5711 24.0288 15.0187 23.5803 15.0187 23.0276C15.0187 22.4749 14.5711 22.0264 14.0174 22.0264H11.0137V8.00895H20.0249V15.5583C20.0249 16.6617 20.5896 17.6499 21.4997 18.1395C21.8251 18.3148 22.0274 18.6532 22.0274 19.0226C22.0274 19.5743 21.5788 20.0239 21.0261 20.0239C20.4734 20.0239 20.0249 19.5743 20.0249 19.0226C20.0249 18.4709 19.5773 18.0214 19.0236 18.0214C18.4699 18.0214 18.0224 18.4699 18.0224 19.0226C18.0224 20.6787 19.3701 22.0264 21.0261 22.0264C22.6822 22.0264 24.0299 20.6787 24.0299 19.0226C24.0299 17.9163 23.4241 16.902 22.4479 16.3763ZM2.03953 5.66504C2.00049 5.56191 1.93741 5.29958 2.20674 5.06429L4.23026 3.18896C5.14139 2.39297 6.15264 1.99848 7.33111 1.99848C8.048 1.99848 8.82697 2.14466 9.68203 2.43602L20.6927 6.00646H2.53215C2.20274 6.00646 2.07758 5.76816 2.03953 5.66504ZM9.01119 20.11L6.42198 17.5208L9.01119 14.9315V20.11ZM6.00746 15.1038V9.92533L8.59668 12.5145L6.00746 15.1038ZM6.00746 19.9378L8.09606 22.0264H6.00746V19.9378ZM9.01119 10.0975L6.9226 8.00895H9.01119V10.0975Z%22 fill=%22white%22/%3E %3C/g%3E %3Cdefs%3E %3CclipPath id=%22clip0_0_4%22%3E %3Crect width=%2224.0299%22 height=%2224.0299%22 fill=%22white%22/%3E %3C/clipPath%3E %3C/defs%3E %3C/svg%3E" );
	--kata-menu-wordmark: url( "data:image/svg+xml,%3Csvg xmlns=%22http://www.w3.org/2000/svg%22 viewBox=%220 0 126.286 27.6913%22 fill=%22none%22%3E%3Cpath d=%22M63.66 0.000732422L65.5554 3.77409H93.3513L95.2471 0.000732422H63.66Z%22 fill=%22%23ffffff%22/%3E %3Cpath d=%22M81.3353 7.54761H77.5619V27.6913H81.3353V7.54761Z%22 fill=%22%23ffffff%22/%3E %3Cpath d=%22M112.38 0L98.4716 27.6908H102.692L112.38 8.40904L122.065 27.6908H126.285L112.38 0Z%22 fill=%22%23ffffff%22/%3E %3Cpath d=%22M46.5248 0L32.6164 27.6908H36.8367L46.5248 8.40904L56.2095 27.6908H60.4297L46.5248 0Z%22 fill=%22%23ffffff%22/%3E %3Cg%3E %3Cpath d=%22M20.245 0.00610352L3.73632 18.07V0.00610352H0V27.6875L3.73632 23.6047L25.3008 0.00610352H20.245Z%22 fill=%22%23ffffff%22/%3E %3Cpath d=%22M15.4709 16.5275L21.0784 27.6909H25.2986L18.1461 13.4475L15.4709 16.5275Z%22 fill=%22%23ffffff%22/%3E %3C/g%3E%3C/svg%3E" );
	--kata-menu-icon-chevron: url( "data:image/svg+xml,%3Csvg preserveAspectRatio=%22none%22 overflow=%22visible%22 style=%22display: block;%22 width=%2215.3016%22 height=%228.07633%22 viewBox=%220 0 15.3016 8.07633%22 fill=%22none%22 xmlns=%22http://www.w3.org/2000/svg%22%3E %3Cpath id=%22Vector%22 d=%22M0.650791 0.759257L7.65079 6.75926L14.6508 0.759257%22 stroke=%22%23000000%22 stroke-width=%222%22 stroke-miterlimit=%2210%22/%3E %3C/svg%3E" );
}

/*
 * The drawer's secondary links are for the drawer; the wide header has its own
 * utility bar directly above, carrying the same links.
 *
 * SELECTED BY STRUCTURE as well as by class, for the same reason the drawer's
 * secondary block is (see "Secondary links" below): nav menu 211 has never
 * carried `kata-nav--secondary`, so the two class selectors here have never
 * matched anything live. That is why אודות and קריירה stood in the 1280 main
 * row ~30px under their own copies in the utility strip, and why adding
 * מאמרים to 211 — which it needed, to reach the drawer at all — made a third
 * duplicate instead of leaving the desktop row alone (QA b966, b972).
 *
 * A top-level row with no children IS a secondary link here: the five rows the
 * frame draws in the main nav are categories and every one of them has
 * children, while אודות, קריירה and מאמרים are single destinations that the
 * utility strip already carries. One menu therefore feeds both states — the
 * drawer shows the quiet links in its two-column block, the wide header leaves
 * them to the strip — with nothing to keep in step by hand.
 *
 * Four class steps out-specify core's own `.wp-block-navigation
 * .wp-block-navigation-item { display: flex }`. The `> ` is load-bearing:
 * submenu children sit in `.wp-block-navigation__submenu-container`, not in
 * `__container`, so the panels under the categories are untouched.
 */
@media ( min-width: 1280px ) {

	.kata-header__primary .kata-nav--secondary,
	.kata-header__primary .kata-nav--lang,
	.kata-header__primary
		.wp-block-navigation__container
		> .wp-block-navigation-item:not( .has-child ) {
		display: none;
	}
}

@media ( max-width: 1279px ) {

	/*
	 * THE DRAWER OWNS THIS WHOLE RANGE, not just phones.
	 *
	 * The navigation block collapses to its toggle at the block's own
	 * breakpoint — 600 — while the drawn mobile bar below runs to 1279. So
	 * without this the full desktop list was laid into a three-column grid
	 * sized for a logo, a phone mark and a toggle: the list measured 747 in a
	 * 781 bar, pushed the logo out to -174, and the document scrolled
	 * sideways at every tablet width. Everything the drawer needs was already
	 * written for this range; only the point at which it takes over was not.
	 *
	 * THIS BOUNDARY IS THE HEADER'S, and the two must stay equal. header.css
	 * hands the bar to the mobile layout at 1279 (TAC-12); if the drawer
	 * stopped before that, the widths in between would show the mobile bar
	 * with a burger that opens nothing, or the desktop list crammed into a
	 * three-column mobile grid — which is the fault this ticket closed.
	 *
	 * Four classes deep because core's rules are three, and they live in a
	 * `min-width: 600px` query that overlaps this one.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container:not( .hidden-by-default ):not( .is-menu-open ) {
		display: none;
	}

	.kata-header__primary
		.wp-block-navigation__responsive-container-open:not( .always-shown ) {
		display: flex;
	}

	/* ---------------------------------------------------------------------
	 * The drawer
	 *
	 * It starts BELOW the header bar rather than covering it, so the logo and
	 * the phone button already in the bar are the ones the drawing shows at the
	 * top — no second copy to keep in step with the first.
	 * ------------------------------------------------------------------ */

	.kata-header__primary .wp-block-navigation__responsive-container.is-menu-open {
		position: fixed;
		/*
		 * Starts BELOW the bar rather than covering it and padding its own
		 * contents down. Padding moved the list but not the panel's own box, so
		 * the drawer still had an opaque surface over the logo — the logo was
		 * painting the whole time, underneath it.
		 */
		/*
		 * Covers the viewport. Starting it below the bar kept the logo visible
		 * for free, but core sets an overflow on this container so the menu can
		 * scroll — and that clipped the close button, which has to sit up in the
		 * bar. Covering everything and lifting the two things that must stay
		 * visible is the version where nothing is clipped and nothing is hidden.
		 */
		inset: 0;
		z-index: 90;
		padding: 0;
		background-color: var( --wp--preset--color--surface );
		/*
		 * The DRAWER does not scroll — the list inside it does.
		 *
		 * Core scrolls this element, and `position: fixed` inside a transformed
		 * ancestor resolves against that ancestor rather than the viewport, so
		 * the close button scrolled away with the content and was gone by the
		 * foot of a short screen. Moving the overflow one level in keeps the
		 * button, the logo and the phone where they belong.
		 */
		overflow: hidden;
	}

	/*
	 * The logo and the phone button ride above the drawer — not the whole bar.
	 *
	 * Raising the bar would put its background over the close button, which
	 * belongs to the drawer's stacking context and sits up in the bar. These two
	 * are the only things the drawing keeps visible up there, and neither
	 * overlaps the X.
	 */
	html.has-modal-open .kata-header__brand,
	html.has-modal-open .kata-header__phone {
		position: relative;
		z-index: 95;
	}

	/*
	 * An opaque strip behind the bar.
	 *
	 * On a screen too short for the menu the drawer scrolls, and its rows travel
	 * up into the band where the logo and the phone button sit — which is
	 * transparent, so the two collided. This masks the scrolling content without
	 * raising the bar itself, which would hide the close button (that lives
	 * inside the drawer and cannot out-stack its own ancestor).
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open::before {
		content: "";
		position: fixed;
		inset-block-start: 0;
		inset-inline: 0;
		block-size: var( --kata-header-height, 95px );
		z-index: 1;
		background-color: var( --wp--preset--color--surface );
		pointer-events: none;
	}

	/* Above that strip, so it stays reachable while the list scrolls under it. */
	.kata-header__primary .wp-block-navigation__responsive-container-close {
		z-index: 2;
	}

	/* The hamburger has become the X; two of them would be one too many. */
	html.has-modal-open .wp-block-navigation__responsive-container-open {
		visibility: hidden;
	}

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__responsive-dialog {
		margin: 0;
		/*
		 * The bar's height plus the frame's own gap beneath it.
		 *
		 * Frame 1000003617 starts the list at 99 with the bar ending at 70, so
		 * there are 29 of clear between the two. Padding to the bar's height
		 * alone left 4, and the first row sat almost against the phone and
		 * close buttons.
		 */
		padding-block-start: calc( var( --kata-header-height, 70px ) + 29px );
	}

	/*
	 * The close button takes the hamburger's place in the bar. It is `fixed`
	 * because it lives inside the dialog, which starts below the bar — and it
	 * has to sit above both.
	 */
	.kata-header__primary .wp-block-navigation__responsive-container-close {
		position: fixed;
		/*
		 * Aligned to the centre of the bar, which the drawer no longer covers.
		 *
		 * Measured, because `fixed` here is not fixed to the viewport: an
		 * ancestor of this button carries a transform, which makes that
		 * ancestor the containing block instead — so the offset is counted from
		 * the top of the drawer, 70 down the screen. The hamburger this
		 * replaces has its centre at y=47, so the button's own top needs to be
		 * 34 minus the header's height, and it tracks if that height changes.
		 */
		inset-block-start: 34px;
		/*
		 * inset-inline-START, which in this RTL document is the physical RIGHT
		 * — where the hamburger it replaces sits. Written as inset-inline-end
		 * it landed on the left, on top of the logo.
		 */
		inset-inline-start: 20px;
		/*
		 * And the opposite side explicitly released. Core already sets an inset
		 * on the far edge; with both set the button stops shrink-wrapping its
		 * icon and stretches the full width of the screen, which put an
		 * invisible slab over the logo — the logo was there and painting, just
		 * underneath a button nobody could see.
		 */
		inset-inline-end: auto;
		z-index: 96;
		padding: 0;
		color: var( --wp--preset--color--white );
	}

	.kata-header__primary .wp-block-navigation__responsive-container-close svg {
		inline-size: 26px;
		block-size: 26px;
	}

	/* ---------------------------------------------------------------------
	 * Rows
	 *
	 * Frame 1000003617 runs 31 in from each edge and starts 99 down. A row is
	 * 52 tall with a rule beneath it, and rows repeat every 84.
	 * ------------------------------------------------------------------ */

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__responsive-container-content {
		display: block;
		/* The list is what scrolls; see the container above. */
		overflow-y: auto;
		max-block-size: calc( 100lvh - var( --kata-header-height, 95px ) - 29px );
		overscroll-behavior: contain;
		padding-block-start: 4px;
		/*
		 * Air under the mark, not a band reserved for it.
		 *
		 * This used to hold up to 160px open at the foot so that a wordmark
		 * anchored to the bottom of the screen could not land on the last rows.
		 * The mark is now the last item in the list itself, so nothing has to be
		 * kept clear of it and a reserved band would simply be dead scroll
		 * BELOW it. What is left is a foot margin.
		 */
		padding-block-end: 32px;
		padding-inline: 31px;
		/*
		 * THE DRAWN COLUMN, not the viewport.
		 *
		 * 2087:6681 is a 395 frame holding a 329 list between 31 gutters, and
		 * that proportion IS the design. Stretched to the viewport instead, the
		 * rows ran 733 at 800 and 993 at 1024 — the label hard against one
		 * edge, the chevron against the other and a dead gutter between them, a
		 * width no frame draws. 391 is 329 plus the two gutters, and because
		 * base.css sets `border-box` that is what this padded box measures, so
		 * the rows come out at the drawn 329 exactly.
		 *
		 * The phone is untouched: at 390 the viewport is already narrower than
		 * the cap, so this changes nothing below about 420.
		 *
		 * `margin-inline-end: auto` sends the slack to the END edge, which in
		 * this RTL document is the physical LEFT — so the column sits against
		 * the right edge, under the burger that opened it, as Creative's spec
		 * asks. Written `margin-inline-start: auto` it lands on the left.
		 */
		max-inline-size: 391px;
		margin-inline-end: auto;
	}

	/*
	 * Two columns, because the foot of the drawer pairs its links.
	 *
	 * Frame 1000003611 sets them in a 2 x 2 block on an 87 pitch, with the
	 * language link on its own line beneath. The main rows simply span both
	 * columns, so one grid serves the whole list rather than a second container
	 * being introduced for four links.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__container {
		display: grid;
		grid-template-columns: 1fr 1fr;
		gap: 0;
		/*
		 * `dense` is what lets the quiet block at the foot fill by COLUMN while
		 * the rows above it still fill by row. The links are placed into named
		 * columns below; without back-filling, a link sent to the end column
		 * after two in the start column would open a THIRD row rather than sit
		 * beside the first. The rows above cannot be back-filled into — they
		 * span both columns and leave no gap — so this reaches the foot only.
		 */
		grid-auto-flow: row dense;
	}

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__container
		> .wp-block-navigation-item {
		grid-column: 1 / -1;
	}

	/* ---------------------------------------------------------------------
	 * Secondary links
	 * ------------------------------------------------------------------ */

	/*
	 * One column each. This has to out-specify the rule above that spans every
	 * item across both columns, or the pairs stack full width.
	 *
	 * SELECTED BY STRUCTURE as well as by class. The three rules below were
	 * written for a `kata-nav--secondary` class, and nav menu 211 does not
	 * carry it on אודות or קריירה — read off
	 * /wp-json/wp/v2/navigation/211 — so none of them has ever matched
	 * anything live: the two links stood full width in a single column with a
	 * rule under each, and each carried an empty 24px box where a category
	 * glyph would go. A top-level row with no children IS a secondary link
	 * here, which says the same thing without a class anyone has to remember
	 * to add — and it will take מאמרים in at once when that is added to the
	 * menu. The class is kept alongside so an item can be flagged explicitly.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__container
		> .kata-nav--secondary,
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		> .wp-block-navigation__responsive-close
		.wp-block-navigation__container
		> .wp-block-navigation-item:not( .has-child ) {
		grid-column: auto;
		/*
		 * The `responsive-close` step is not decoration: the rule that gives
		 * every top-level row its bottom rule carries it, so without it this
		 * override only TIED on specificity and lost on order. Seen live at
		 * 800 the moment מאמרים was added — the pair kept a rule under it and
		 * מאמרים, alone on its line, drew a HALF-WIDTH line across one grid
		 * column. 2087:6681 rules the primary rows and leaves the quiet block
		 * below them unruled.
		 */
		border-block-end: 0;
	}

	/*
	 * WHICH column each quiet link takes — 2087:6681 fills the foot by column,
	 * not by row.
	 *
	 * The frame draws two column frames down there, not one wrapping list:
	 * אודות over קריירה on the right, מאמרים (and, when it had a destination,
	 * פניות דיירים) on the left. Live it filled by row instead — the first two
	 * sharing a line and the third orphaned beneath, which reads as a wrapping
	 * accident rather than two groups.
	 *
	 * The split is made in PHP, where the number of links is known: the first
	 * half take `-a`, the remainder `-b` (see kata_header_nav_* in
	 * functions.php). In Hebrew column 1 is the right-hand one, so `-a` is the
	 * right column the frame draws אודות and קריירה in.
	 *
	 * `.wp-block-navigation-item` and `:not( .has-child )` are both carried
	 * here for WEIGHT, not for matching — every quiet link is already both.
	 * The rule these have to beat is the `grid-column: auto` above, which
	 * selects the same links structurally and counts `:not( .has-child )` as a
	 * class: at six classes against its seven these lost on specificity
	 * whatever the source order, and the foot would have gone on filling by
	 * row with מאמרים orphaned beneath — the exact accident being fixed. Eight
	 * wins outright, which is why this is not left to order.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		> .wp-block-navigation__responsive-close
		.wp-block-navigation__container
		> .wp-block-navigation-item.kata-nav--secondary-a:not( .has-child ) {
		grid-column: 1;
	}

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		> .wp-block-navigation__responsive-close
		.wp-block-navigation__container
		> .wp-block-navigation-item.kata-nav--secondary-b:not( .has-child ) {
		grid-column: 2;
	}

	/*
	 * The rule above the pair, across both columns.
	 *
	 * The two are flagged in the markup rather than selected by position: an
	 * nth-of-type here would count every list item, so adding or removing a
	 * category above would silently move the rule.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.kata-nav--secondary-top {
		border-block-start: 1px solid rgba( 255, 255, 255, 0.25 );
	}

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.kata-nav--secondary
		.wp-block-navigation-item__content,
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.kata-nav--lang
		.wp-block-navigation-item__content,
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__container
		> .wp-block-navigation-item:not( .has-child )
		> .wp-block-navigation-item__content {
		justify-content: center;
		color: rgba( 255, 255, 255, 0.72 );
	}

	/* No category glyph on these — they are not categories. */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.kata-nav--secondary
		.wp-block-navigation-item__content::before,
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.kata-nav--lang
		.wp-block-navigation-item__content::before,
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__container
		> .wp-block-navigation-item:not( .has-child )
		> .wp-block-navigation-item__content::before {
		content: none;
	}

	/* The language link takes its own line, ruled off above. */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.kata-nav--lang {
		grid-column: 1 / -1 !important;
		border-block-start: 1px solid rgba( 255, 255, 255, 0.25 );
		border-block-end: 0;
	}

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		> .wp-block-navigation__responsive-close
		.wp-block-navigation__container
		> .wp-block-navigation-item {
		/*
		 * The ROW is the flex line, not the link.
		 *
		 * Core puts the submenu chevron OUTSIDE the button, as a sibling inside
		 * this item — so with `display: block` here the chevron dropped onto a
		 * line of its own beneath the label, which is why it would not centre
		 * against it however it was aligned. Laying the item out as a centred
		 * flex row puts the two back on one line; the submenu panel wraps to a
		 * full-width line below them.
		 */
		/*
		 * A GRID, not a wrapping flex row.
		 *
		 * Core puts the chevron outside the button, so the row has to place two
		 * things side by side and the submenu panel underneath. As a wrapping
		 * flex row the button kept claiming the whole line and pushing the
		 * chevron onto a second one, whatever basis it was given. Two columns
		 * state the intent directly: the label takes what is left, the chevron
		 * takes what it needs, and the panel spans both.
		 */
		display: grid;
		grid-template-columns: minmax( 0, 1fr ) auto;
		align-items: center;
		/*
		 * Frame 174766 and its siblings sit at 352, 436, 520 and 604 — a pitch
		 * of 84 for a row that is 52 tall. So 28 of content with 12 above and
		 * below, the rule on the row's own edge, and 31 clear before the next.
		 */
		/*
		 * The gap between rows is PADDING, not a margin below the rule.
		 *
		 * Same 84 pitch either way, but with 12 of padding and 31 of margin the
		 * label had 43 of clear above it and 12 below — so it sat visibly low in
		 * the band between one rule and the next, even though it was perfectly
		 * centred in its own line box. Splitting the space evenly centres it
		 * where the eye actually reads it: between the rules.
		 */
		padding-block: 27px;
		border-block-end: 1px solid rgba( 255, 255, 255, 0.25 );
	}

	/*
	 * The row itself: label and glyph at the reading edge, chevron at the far
	 * one. `row-reverse` rather than `justify-content`, because the glyph has
	 * to sit outside the label and both have to stay together when the label
	 * wraps.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__submenu-container {
		grid-column: 1 / -1;
	}

	/*
	 * The link shares the line with the chevron.
	 *
	 * At its natural basis the link claimed the whole row, and since the row
	 * wraps — it has to, so the submenu panel can take a line of its own — the
	 * chevron was pushed onto a second line and sat below the label instead of
	 * beside it. A zero basis lets it take only what is left.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__container
		> .wp-block-navigation-item
		> .wp-block-navigation-item__content {
		grid-column: 1;
		min-inline-size: 0;
	}

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation-item__content {
		display: flex;
		align-items: center;
		justify-content: flex-start;
		/* Frame 1000003613: 24 between the glyph and the label. */
		gap: 24px;
		padding: 0;
		min-block-size: 28px;
		color: var( --wp--preset--color--white );
		/* 24px — between the `lg` and `xl` steps, so it is set directly. */
		font-size: 24px;
		/*
		 * The frame gives the label a 28 box, and 24px type sets a line box
		 * taller than that on its own — which pushed the row's pitch from the
		 * drawn 84 out to 93. Stated explicitly so the rhythm comes from the
		 * drawing rather than from the font's default leading.
		 */
		line-height: 28px;
		text-decoration: none;
	}

	/*
	 * The category glyph, from the frame's own icon layers. A mask rather than
	 * an <img>, so it takes the row's colour and needs no markup of its own —
	 * a navigation-link has nowhere to put an image.
	 */
	/*
	 * The category glyph, straight from the frame's own icon layers.
	 *
	 * A background IMAGE, not a mask: these are drawn in colour — a pink heart,
	 * a blue building, a green house — and a mask would flatten all five to the
	 * row's white. Masking is right for the chevron below, which is monochrome
	 * and has to follow the text.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation-item__content::before {
		content: "";
		/*
		 * order 0 puts it FIRST in the row, which in this RTL document is the
		 * rightmost position — where the frame draws it, outside the label.
		 * At order 3 it fell past both the label and the chevron and ended up
		 * on the far left.
		 */
		order: 0;
		flex: none;
		inline-size: 24px;
		block-size: 24px;
		background-position: center;
		background-repeat: no-repeat;
		background-size: contain;
	}

	.kata-nav--projects > .wp-block-navigation-item__content::before {
		background-image: var( --kata-menu-icon-projects );
	}

	.kata-nav--income > .wp-block-navigation-item__content::before {
		background-image: var( --kata-menu-icon-income );
	}

	.kata-nav--urban > .wp-block-navigation-item__content::before {
		background-image: var( --kata-menu-icon-urban );
	}

	.kata-nav--development > .wp-block-navigation-item__content::before {
		background-image: var( --kata-menu-icon-development );
	}

	.kata-nav--construction > .wp-block-navigation-item__content::before {
		background-image: var( --kata-menu-icon-construction );
	}

	/*
	 * מגורים — the live menu's first row, which the frames do not name.
	 *
	 * 2087:6681 draws five rows (פרויקטים, נכסים מניבים, התחדשות עירונית,
	 * ייזום, ביצוע) and the five variables above are their own icon layers. The
	 * menu live carries three, and only two of them — `--urban` and `--income`
	 * — have a name in the frame. `--residential` had no glyph declared at all,
	 * which is why Creative found the first row bare while the two under it
	 * were not: a missing declaration, not a missing class.
	 *
	 * It takes the frame's home-heart, drawn for פרויקטים: of the five that is
	 * the one that means homes. Whether the drawer should carry the drawn five
	 * instead of these three is content and is the client's to answer; this row
	 * keeps its glyph either way, and if the five arrive the five rules above
	 * already cover them.
	 */
	.kata-nav--residential > .wp-block-navigation-item__content::before {
		background-image: var( --kata-menu-icon-projects );
	}

	/*
	 * The chevron sits at the far edge and turns when the row opens. Core emits
	 * its own arrow in a `__submenu-icon` span; it is replaced rather than
	 * restyled, because the drawn mark is a different shape.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__submenu-icon {
		display: block;
		/* Second column: the far edge, level with the label. */
		grid-column: 2;
		padding: 0;
		inline-size: 15px;
		block-size: 8px;
		background-color: currentcolor;
		-webkit-mask-image: var( --kata-menu-icon-chevron );
		mask-image: var( --kata-menu-icon-chevron );
		-webkit-mask-position: center;
		mask-position: center;
		-webkit-mask-repeat: no-repeat;
		mask-repeat: no-repeat;
		-webkit-mask-size: contain;
		mask-size: contain;
		transition: transform 240ms ease;
	}

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__submenu-icon svg {
		display: none;
	}

	/*
	 * Turned on the OPEN row, read from our own attribute.
	 *
	 * It used to read `[aria-expanded="true"]`, which core binds to its own
	 * interactivity state and had reading true on every row the moment the
	 * drawer opened — so every chevron in the drawer pointed up at a row that
	 * was not open. See assets/js/menu-accordion.js.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		[data-kata-open]
		> .wp-block-navigation__submenu-icon {
		transform: rotate( 180deg );
	}

	/* ---------------------------------------------------------------------
	 * The expanded panel
	 *
	 * Black, full-bleed past the list's 31 gutter, with its own separators —
	 * Group 1000003263 in the frame. Rows inside are 28 tall on a 74 pitch.
	 * ------------------------------------------------------------------ */

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__submenu-container {
		position: static;
		inline-size: auto;
		margin-block: 12px -12px;
		margin-inline: -31px;
		padding-inline: 31px;
		border: 0;
		/*
		 * `!important` because core sets the submenu transparent inside an open
		 * overlay — it assumes the panel should inherit the drawer's colour,
		 * and the drawing has it black against the drawer's grey.
		 */
		background-color: var( --wp--preset--color--black ) !important;
		opacity: 1;
		visibility: visible;
	}

	/*
	 * Collapsed until asked for — keyed to OUR attribute, not core's.
	 *
	 * Core's overlay flattens the menu and shows every submenu at once, which
	 * is right for a plain list and wrong for the drawn accordion. This rule
	 * used to read `[aria-expanded="false"]`, and that is the whole of the
	 * fault QA reported: core binds that attribute with
	 * `data-wp-bind--aria-expanded="state.isMenuOpen"`, so every row read TRUE
	 * from the moment the drawer opened, the selector matched nothing, and all
	 * three panels stood open with the toggle unable to shut them. The same
	 * three children printed three times over, and the structure the drawer
	 * exists to show was invisible.
	 *
	 * Both rules are scoped to `kata-menu--js`, which menu-accordion.js writes
	 * once it is running. Without it nothing is hidden and the drawer falls
	 * back to the flattened list — see that file for why that fallback matters.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open.kata-menu--js
		.wp-block-navigation__submenu-container {
		display: none;
	}

	/* One more class and one attribute than the rule above, so it wins. */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open.kata-menu--js
		[data-kata-open]
		> .wp-block-navigation__submenu-container {
		display: block;
	}

	/*
	 * The row fills the panel and the link fills the row.
	 *
	 * Left to itself each link shrink-wraps its own text, so `justify-content`
	 * had nothing to distribute and the three labels sat ragged at 199, 198 and
	 * 204 instead of sharing one edge.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__submenu-container
		> .wp-block-navigation-item {
		display: block;
		border-block-start: 1px solid rgba( 255, 255, 255, 0.18 );
	}

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__submenu-container
		.wp-block-navigation-item__content {
		inline-size: 100%;
	}

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__submenu-container
		.wp-block-navigation-item__content {
		/*
		 * Right-aligned, not centred. Frame 1000003609 sets every child's right
		 * edge at the same 209 of its 257 box — 48 in from the list's reading
		 * edge — which is why the three labels of different lengths line up on
		 * that side and ragged on the other.
		 */
		justify-content: flex-start;
		padding-block: 23px;
		padding-inline-start: 48px;
		font-size: 24px;
		line-height: 28px;
	}

	/* No glyph and no chevron on the children — the drawing gives them neither. */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__submenu-container
		.wp-block-navigation-item__content::before {
		content: none;
	}

	/* ---------------------------------------------------------------------
	 * The wordmark
	 *
	 * Group 2 in the frame: the KATA letterforms very large at the foot of the
	 * drawer, running off both edges. Decoration, so it is a background on the
	 * dialog rather than markup — nothing to read, nothing to tab to.
	 *
	 * Drawn from the same path data as the header's logo, lifted out of
	 * Wordmark.php, so the two cannot drift apart.
	 * ------------------------------------------------------------------ */

	/*
	 * IN FLOW at the foot of the list, and BRIGHT — Creative b984, which
	 * overrules the dimmed version this replaces.
	 *
	 * The history is worth keeping, because both earlier attempts were wrong in
	 * the same way. The mark began as a full-strength background on the
	 * drawer's fixed panel, sized to the VIEWPORT: 128% of 1024 is 1310 wide
	 * against the 505 the frame draws, so its WHITE letterforms ran under the
	 * WHITE label of the third row and took the first letters of מסחר with
	 * them. It was then dimmed to a fifth, which stopped the words being lost
	 * but cost the foot its only presence — and 2087:6681 draws the mark bright.
	 * (2087:6777 draws it bright too, with the grown list half-swallowed by it;
	 * that is an unresolved overlap in a mockup, not a treatment. A faded live
	 * row is one a visitor can neither read nor tap, so the frame set has
	 * exactly one shippable foot and it is 6681's.)
	 *
	 * Both attempts were ANCHORED TO THE VIEWPORT, which is the actual fault:
	 * a mark pinned to the bottom of the screen must cross whatever the list
	 * happens to reach, and above phone width it also escaped the ~330 column
	 * entirely and was cropped by the screen edge. In flow it cannot collide
	 * with anything: it is the last item in the grid, below the quiet links,
	 * and nothing is underneath it. When a panel opens and the content grows it
	 * is pushed down out of view, which is correct — it is a signature, not a
	 * control.
	 *
	 * Two background layers, so one element carries both the hairline 6681
	 * draws above the mark and the mark itself:
	 *   1. a 1px line across the full width of the COLUMN, at the top;
	 *   2. the wordmark at 134% of the column, centred, clipped by the column —
	 *      the frame's own relationship, where a 442-wide mark sits in a 329
	 *      column and runs off both edges.
	 * The ratio gives the mark its drawn height at that scale (126.286:27.6913
	 * × 1.34) plus about 24px of air under the hairline.
	 */
	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__container::after {
		content: "";
		grid-column: 1 / -1;
		margin-block-start: 24px;
		aspect-ratio: 126.286 / 45;
		background-image:
			linear-gradient(
				rgba( 255, 255, 255, 0.25 ),
				rgba( 255, 255, 255, 0.25 )
			),
			var( --kata-menu-wordmark );
		background-repeat: no-repeat, no-repeat;
		background-position: center top, center bottom;
		background-size: 100% 1px, 134% auto;
		pointer-events: none;
	}

	.kata-header__primary
		.wp-block-navigation__responsive-container.is-menu-open
		.wp-block-navigation__responsive-container-content {
		position: relative;
	}
}