/* ft-consent.css  1.0.0
   Consent bar for the two Google Analytics cookies (_ga, _ga_*).
   Replaces the webtoffee-cookie-consent plugin (about 108KB of CSS, JS,
   inline config and vendor SVG) with roughly 3KB of CSS + JS.

   Byte-identical on the 3 parents. Every string and the GA id come from
   ftConsentCfg, localised per site in functions.php.

   Compliance note, do not "improve" this away: the Accept and Refuse buttons
   are deliberately IDENTICAL in size, weight, colour, border and padding.
   Refusing has to be exactly as easy as accepting, so neither button may be
   restyled to stand out. The plugin got this wrong (filled green Accept
   against an outline Reject). */

.ft-consent{
	position:fixed;
	left:0;
	right:0;
	bottom:0;
	/* Above the sticky listing filter (10001) and the 100000 band, below the
	   full-screen .overlay (seating plans / maps) which must keep covering it. */
	z-index:100001;
	background:var(--ft-hero-bg,#13274d);
	color:#fff;
	border-top:3px solid var(--ft-blue,#4098D8);
	box-shadow:0 -2px 12px rgba(0,0,0,.28);
	font-size:14px;
	line-height:1.5;
	/* No entrance animation on purpose, do not add one back. The first version
	   appended the bar at translateY(100%) and let JS add a class on the next
	   animation frame. requestAnimationFrame does not fire in a hidden tab, so
	   a page opened in a background tab kept the bar parked below the viewport:
	   no bar, no choice recorded, and GA never loading for someone who would
	   have accepted. Being visible is now the element's plain default state,
	   which cannot fail. */
}

.ft-consent-in{
	/* Matches the 1080px parent content container. */
	max-width:1080px;
	margin:0 auto;
	padding:14px 16px;
	display:flex;
	align-items:center;
	gap:16px;
	flex-wrap:wrap;
}

.ft-consent-txt{flex:1 1 320px;margin:0;}
/* Every anchor state is named here on purpose. The theme's style.css carries
   `a{color:#2d6187}`, `a:visited{color:#2d6187}`, `a:active,a:hover{color:#4098d8}`
   and `a:focus{outline:none}`. Those state rules score (0,1,1), exactly the
   same as a bare `.ft-consent-txt a`, and ft-consent.css is enqueued BEFORE
   style.css, so the theme won every tie. The visible symptom: for anyone who
   had already opened /cookies/ the link rendered #2d6187 on navy, which is
   2.22:1 and effectively invisible, while an unvisited link looked correct.
   That is also why the focus ring is restored below, `a:focus{outline:none}`
   was removing it.

   Adding the class makes each selector (0,2,1), which clears the theme.
   Do not collapse these back into one bare selector, and do not rely on load
   order to save it: this file is deliberately enqueued early. */
.ft-consent-txt a,
.ft-consent-txt a:link,
.ft-consent-txt a:visited,
.ft-consent-txt a:hover,
.ft-consent-txt a:focus,
.ft-consent-txt a:active{
	color:#fff;
	font-weight:600;
	text-decoration:underline;
	text-underline-offset:3px;
}
.ft-consent-txt a:hover,
.ft-consent-txt a:active{text-decoration-thickness:2px;}
.ft-consent-txt a:focus{outline:3px solid var(--ft-vip,#f0c65c);outline-offset:2px;}
.ft-consent-txt a:focus:not(:focus-visible){outline:none;}
.ft-consent-txt a:focus-visible{outline:3px solid var(--ft-vip,#f0c65c);outline-offset:2px;}

.ft-consent-btns{display:flex;gap:10px;flex:0 0 auto;}

.ft-consent-btn{
	font:inherit;
	font-weight:600;
	min-width:124px;
	padding:10px 20px;
	border:2px solid #fff;
	border-radius:4px;
	background:#fff;
	color:var(--ft-hero-bg,#13274d);
	cursor:pointer;
}
.ft-consent-btn:hover{background:var(--ft-hero-h1-sub,#e7eefb);}
/* :focus first so browsers without :focus-visible still get a ring, then the
   ring is withdrawn from mouse users where :focus-visible is understood. */
.ft-consent-btn:focus{outline:3px solid var(--ft-vip,#f0c65c);outline-offset:2px;}
.ft-consent-btn:focus:not(:focus-visible){outline:none;}
.ft-consent-btn:focus-visible{outline:3px solid var(--ft-vip,#f0c65c);outline-offset:2px;}

@media (max-width:600px){
	.ft-consent-in{padding:12px 14px;gap:12px;}
	.ft-consent-btns{width:100%;}
	/* Equal width halves: still identical to each other. */
	.ft-consent-btn{flex:1 1 0;min-width:0;padding:11px 12px;}
}


/* Shown only when the bar is reopened from a "Cookie preferences" link, to
   report the choice already on file. Muted on purpose: it is a status line,
   not a third action. */
.ft-consent-state{display:block;margin-top:4px;color:var(--ft-hero-meta,#c7d3ec);}