/* Team card navigation (About Us) — see tnc-team-card-link.js header for
   the full explanation. Replaces an earlier click-to-expand accordion.

   Chasing z-index alone against this card's inner markup turned out to be
   whack-a-mole: Elementor gives several inner elements (.team-social-list,
   and apparently at least one other wrapper near the name/title area,
   confirmed by hit-testing) their own non-auto z-index per-instance, each
   independently capable of ending up above a simple z-index:1 overlay
   depending on which sub-area of the card you test. Rather than find and
   out-rank every one of them individually, deny pointer events to
   everything inside the card by default and explicitly allow only the two
   things that should ever capture a click: this overlay, and the real
   LinkedIn link. That makes hit-testing exclusive regardless of how many
   stray z-index values Elementor happens to set elsewhere in the card. */
.tnc-team-card * {
	pointer-events: none;
}

.tnc-team-card {
	position: relative; /* containing block for the overlay link below */
}

.tnc-team-card-link,
.team-social-list a {
	pointer-events: auto;
}

.tnc-team-card-link {
	/* Full-card overlay, not a wrapper around existing content — the
	   card's inner markup differs per person and is itself a nested
	   flex/grid layout that a wrapping anchor would disrupt.

	   z-index:0, not 1: Elementor gives .team-social-list its own
	   explicit z-index of 1 per-instance, so this needs to sit below it
	   for the LinkedIn link to paint on top at its own position —
	   confirmed by hit-testing the icon's exact pixel. The pointer-events
	   rule above is what keeps the REST of that subtree's area
	   click-through to this overlay despite it painting higher; z-index
	   only still matters for the one element (the LinkedIn link) that's
	   still allowed to capture a click there. */
	position: absolute;
	inset: 0;
	z-index: 0;
	width: 100%;
	height: 100%;
}