@charset "UTF-8";
/*!
 * FAZ Cookie Manager — Cookie Policy frontend styles.
 *
 * Deliberately minimal: inherits font, colours, spacing from the host
 * theme. The only interventions are:
 *   1. Lift the typographic max-width constraint that block themes like
 *      Twenty Twenty-Four/Five impose via `.entry-content` (60ch) — which
 *      makes a long legal document feel cramped.
 *   2. Style the optional disclaimer so it is visually distinct from
 *      body copy (warning-coloured callout, light backdrop). Visibility
 *      and text are now admin-configurable; CSS still gives it the
 *      callout treatment whenever it is rendered.
 *   3. Style the per-category accordion (<details>/<summary>) and the
 *      cookie table inside it. Accordion is HTML5-native, JS-free,
 *      keyboard-accessible. The table inside uses a mobile-friendly
 *      data-label fallback so the layout collapses to a card stack on
 *      narrow screens without media queries fighting the theme.
 *   4. Neutralise <code> inside the policy. The policy uses <code> for
 *      cookie names and technical tokens; many themes style the global
 *      `code {}` element with a coloured background + border (often via
 *      their own `--theme-color-*` custom properties), which looks out of
 *      place inside a legal document. We force a transparent, border-less,
 *      inherit-colour monospace token so the policy renders neutrally on
 *      any theme.
 *
 * Anything else (headings, link colours, paragraph rhythm) is theme.
 */

/* 1. Fill the available column. Most block themes constrain content to ~60ch. */
.faz-cookie-policy {
	max-width: none;
	width: 100%;
	box-sizing: border-box;
}

/* 4. Neutral <code> regardless of the active theme. `!important` is a
   deliberate, tightly-scoped exception to this file's otherwise no-!important
   convention: a theme's `code {}` rule may itself be flagged !important or use
   an equal-specificity `.entry-content code` selector, and the policy must look
   clean on every theme. Only the box/colour properties are forced; the
   monospace family is left to the theme/UA. */
.faz-cookie-policy code {
	border: 0 !important;
	background: transparent !important;
	background-color: transparent !important;
	color: inherit !important;
	box-shadow: none !important;
	padding: 0;
}

/* 3. Cookie list (auto-populated). One <details> per category. */
.faz-cookie-policy-category {
	margin: 1em 0 1.5em 0;
}

.faz-cookie-policy-details {
	border: 1px solid rgba(0, 0, 0, 0.08);
	border-radius: 6px;
	margin: 0.5em 0;
	background: var(--faz-policy-card-bg, transparent);
}

.faz-cookie-policy-details + .faz-cookie-policy-details {
	margin-top: 0.6em;
}

/* Summary layout — selector specificity is intentionally higher
   (details.X > summary.Y) so block themes that hit `summary` with
   `display: block` via .entry-content selectors lose the cascade
   battle. The category heading inside is forced to inline-flex so
   the theme's default `h3 { display: block; width: 100% }` cannot
   push the count badge onto a second line. */
details.faz-cookie-policy-details > summary.faz-cookie-policy-summary {
	cursor: pointer;
	list-style: none;
	padding: 0.75em 1em;
	display: flex;
	align-items: center;
	gap: 0.75em;
	user-select: none;
	transition: background-color 120ms ease;
}

details.faz-cookie-policy-details > summary.faz-cookie-policy-summary:hover,
details.faz-cookie-policy-details > summary.faz-cookie-policy-summary:focus-visible {
	background: rgba(0, 0, 0, 0.04);
	outline: none;
}

/* Hide the native marker on every engine (Blink/WebKit + Gecko + spec). */
details.faz-cookie-policy-details > summary.faz-cookie-policy-summary::-webkit-details-marker {
	display: none;
}
details.faz-cookie-policy-details > summary.faz-cookie-policy-summary::marker {
	content: '';
}

/* Custom chevron — sits left of the title, rotates on [open]. */
details.faz-cookie-policy-details > summary.faz-cookie-policy-summary::before {
	content: '';
	display: inline-block;
	width: 0.55em;
	height: 0.55em;
	border-right: 2px solid currentColor;
	border-bottom: 2px solid currentColor;
	transform: rotate(-45deg);
	transition: transform 150ms ease;
	flex: 0 0 auto;
}

details.faz-cookie-policy-details[open] > summary.faz-cookie-policy-summary::before {
	transform: rotate(45deg);
}

/* Category name. The renderer emits this as <span role="heading"
   aria-level="3"> (changed from <h3> in 1.16.2 because block-level
   headings inside <summary> get coerced to display:block by every
   block-theme reset and break the inline layout). Force inline-flex
   + flex:1 so the chevron, name, count all sit on ONE row. */
details.faz-cookie-policy-details > summary.faz-cookie-policy-summary > .faz-cookie-policy-category-name {
	display: inline-flex;
	align-items: center;
	margin: 0;
	padding: 0;
	width: auto;
	font-size: 1.05em;
	font-weight: 600;
	line-height: 1.3;
	flex: 1 1 auto;
}

details.faz-cookie-policy-details > summary.faz-cookie-policy-summary > .faz-cookie-policy-count {
	display: inline-flex;
	align-items: center;
	width: auto;
	font-size: 0.85em;
	color: var(--faz-policy-muted, #666);
	font-weight: normal;
	white-space: nowrap;
	flex: 0 0 auto;
}

.faz-cookie-policy-details-body {
	padding: 0.25em 1em 1em 1em;
}

/* Cookie table inside the accordion. */
.faz-cookie-policy-table {
	width: 100%;
	border-collapse: collapse;
	margin: 0.75em 0 0;
	font-size: 0.92em;
}

.faz-cookie-policy-table th,
.faz-cookie-policy-table td {
	text-align: left;
	padding: 0.55em 0.7em;
	vertical-align: top;
	border-bottom: 1px solid rgba(0, 0, 0, 0.06);
}

.faz-cookie-policy-table thead th {
	font-weight: 600;
	border-bottom: 2px solid rgba(0, 0, 0, 0.12);
	background: rgba(0, 0, 0, 0.02);
}

.faz-cookie-policy-table code {
	/* Box/colour neutralised by the `.faz-cookie-policy code` rule above; only
	   nudge the cookie-name tokens to a slightly smaller monospace size. */
	font-size: 0.95em;
}

/* Mobile: collapse the table into a card-per-row layout using
   the data-label attributes the renderer emits on each <td>. */
@media (max-width: 600px) {
	.faz-cookie-policy-table thead {
		clip: rect(0 0 0 0);
		clip-path: inset(50%);
		height: 1px;
		width: 1px;
		overflow: hidden;
		position: absolute;
		white-space: nowrap;
	}

	.faz-cookie-policy-table,
	.faz-cookie-policy-table tbody,
	.faz-cookie-policy-table tr,
	.faz-cookie-policy-table td {
		display: block;
		width: 100%;
	}

	.faz-cookie-policy-table tr {
		border: 1px solid rgba(0, 0, 0, 0.08);
		border-radius: 4px;
		padding: 0.4em 0.5em;
		margin: 0.5em 0;
	}

	.faz-cookie-policy-table td {
		border: 0;
		padding: 0.2em 0;
	}

	.faz-cookie-policy-table td::before {
		content: attr(data-label) ': ';
		font-weight: 600;
		display: inline-block;
		margin-right: 0.4em;
	}
}

/* 2. Disclaimer — admin-configurable callout. */
.faz-cookie-policy-disclaimer {
	margin-top: 2em;
	padding: 0.85em 1em;
	background: var(--faz-disclaimer-bg, #fff5d6);
	border-left: 4px solid var(--faz-disclaimer-accent, #d4a017);
	font-size: 0.9em;
	line-height: 1.55;
}

/* 3. International data transfers (Schrems II) — neutral transparency block.
   Purely informational: it never gates or reweights any consent control. */
.faz-cookie-policy-transfers {
	margin-top: 2em;
	padding: 1em 1.15em;
	background: var(--faz-transfer-bg, #f1f5f9);
	border-left: 4px solid var(--faz-transfer-accent, #64748b);
	border-radius: 4px;
}

.faz-cookie-policy-transfers-title {
	margin: 0 0 0.4em;
	font-size: 1.15em;
}

.faz-cookie-policy-transfers-list {
	margin: 0.6em 0 0;
	padding-left: 1.2em;
	line-height: 1.55;
}

.faz-cookie-policy-transfers-list code {
	font-size: 0.92em;
}

/* Per-row indicator inside the cookie inventory table. */
.faz-cookie-policy-transfer {
	display: block;
	margin-top: 0.35em;
	font-size: 0.82em;
	color: var(--faz-transfer-fg, #475569);
}
/**
 * All of the CSS for your public-facing functionality should be
 * included in this file.
 */[class*=tec-events-elementor-event-widget]{color:var(--tec-color-text-primary);font-family:var(--tec-font-family-sans-serif);font-size:1rem;font-weight:var(--tec-font-weight-regular);line-height:var(--tec-line-height-3);margin:0 0 var(--tec-spacer-0) 0;padding:0}[class*=tec-events-elementor-event-widget] [class*=tec-events-elementor-event-widget]{color:inherit;font-family:inherit;font-size:inherit;font-weight:inherit;line-height:inherit;margin:inherit;padding:inherit}[class*=tec-events-elementor-event-widget] a,a[class*=tec-events-elementor-event-widget]{border-bottom-color:initial;-webkit-text-decoration:underline;text-decoration:underline}.e-con-inner [class*=elementor-widget-tec_elementor_widget]:not(:last-child),.elementor-section:not(.elementor-top-section) [class*=elementor-widget-tec_elementor_widget]:not(:last-child){margin-block-end:var(--tec-spacer-3)}.tec-events-elementor-widget-empty{background-color:var(--tec-color-background-secondary);color:var(--tec-color-text-secondary);font-size:1rem;font-weight:var(--tec-font-weight-regular);line-height:var(--tec-line-height-3);padding:1em;text-align:center}


/*
Theme Name: Faith Connect
Theme URI: https://faith-connect.cmsmasters.net/
Author: cmsmasters
Author URI: https://cmsmasters.net/
Description: Faith Connect - Church & Religion WordPress Elementor Theme is a perfect theme for traditional and modern churches and religious organizations, church events and other community events, church donations, etc. This WordPress theme has all the needed functionality for churches including Sermons, Campaigns, Profiles and Ministries custom post types, Donations Functionality and Events support. It comes with a full WooCommerce plugin integration to sell goods from your church website to collect funds for your religious projects and church.
Version: 1.1.3
Tested up to: 6.6
Requires PHP: 7.4
License:
License URI:
Text Domain: faith-connect
Domain Path: /theme-config/languages
Copyright: cmsmasters 2024 / All Rights Reserved
Tags: one-column, two-columns, three-columns, four-columns, left-sidebar, right-sidebar, custom-background, custom-colors, custom-header, custom-menu, editor-style, featured-image-header, featured-images, flexible-header, full-width-template, microformats, post-formats, rtl-language-support, sticky-post, theme-options, threaded-comments, translation-ready
*/


.sticky,
.bypostauthor,
.screen-reader-text {
  outline: none;
}