/*
 * mcmc-search — the ONLY rules from facetwp/assets/css/front.css and
 * facetwp/assets/vendor/fComplete/fComplete.css that reach an element on pages 40
 * and 1292, reproduced verbatim under the same selectors, and nothing else.
 *
 * ⛔ THE SET IS MEASURED, NOT JUDGED. `reports/MCMC-BUILD-C/<ts>-tools/`
 * `match-selectors.js` runs every selector in both stylesheets through
 * `document.querySelectorAll` IN A REAL BROWSER, AFTER the five Code Snippets have
 * run — because FacetWP injects the facet markup client-side and fComplete adds
 * `fcomplete-enabled` and a whole `.fcomplete-wrap` subtree of its own, so a scan of
 * the server HTML would answer for a page that never exists. Result, 7 Sept 2026:
 *
 *     stylesheet       selectors   match an element on /find-your-cause/   on /
 *     front.css               70                                      1        1
 *     fComplete.css            5                                      3        3
 *
 * ⭐ ONE RULE OF SEVENTY. `.facetwp-facet { margin-bottom: 40px }` is the whole of
 * what front.css does to this site; the other 69 selectors are checkboxes, radios,
 * fSelect, sliders, star ratings, date pickers, proximity search and the AJAX
 * loading overlay — facet types this site does not use and an AJAX refresh it will
 * no longer have. They are not copied.
 *
 * ⚠ AND THE ONE RULE IS ITSELF OVERRIDDEN EVERYWHERE IT LANDS. `custom_css` post 362
 * sets a 5px vertical rhythm on `.mcmc-search .facetwp-facet`, `.mcmc-facet-btn
 * .facetwp-facet` and `.elementor-widget .facetwp-facet[data-name="reset"]`, all
 * more specific, and the measured computed `margin-bottom` on every facet on both
 * pages is 5px, not 40px. It is copied anyway: it is a rule that matches, the bar is
 * that nothing changes, and the cost of being wrong about which override wins is a
 * 35px gap appearing under a control nobody was looking at.
 *
 * ⛔ NOT COPIED, AND NAMED SO THE ABSENCE IS NOT MISTAKEN FOR AN OVERSIGHT: everything
 * in `custom_css` post 362. That is the client's own stylesheet, it is not FacetWP's
 * to take, this seat has no authority over post 362, and it keeps working untouched
 * because every `.facetwp-*` class and every `data-name` it selects on is reproduced
 * by the four widgets. The one selector it carries that this build does NOT satisfy
 * is `.elementor-widget-facetwp` — see the note at the end of this file.
 */

/* ------------------------------------------------------------------ front.css */

/* facetwp/assets/css/front.css:1-3 — verbatim. */
.mc-facet {
    margin-bottom: 40px;
}

/* -------------------------------------------------------------- fComplete.css */

/*
 * facetwp/assets/vendor/fComplete/fComplete.css — the whole file, 422 bytes,
 * verbatim, under the same class names.
 *
 * ⚠ THREE OF THE FIVE WERE MEASURED MATCHING AND TWO WERE NOT, AND ALL FIVE ARE
 * COPIED. `.fcomplete-wrap`, `.fcomplete-status` and `.fcomplete-hidden` exist on
 * both pages the moment fComplete constructs — measured, 1 on the directory and 2 on
 * HOME, one per search box. `.fcomplete-result` and `.fcomplete-result:hover` match
 * ZERO elements in the idle state and match exactly when a visitor has typed three
 * characters and the suggestion list has rendered — a state a page-load scan cannot
 * reach. Dropping them because the idle measurement returned zero would delete the
 * padding and the hover on the only part of this control a visitor ever clicks.
 */
.mc-ac {
    position: absolute;
    border: 1px solid #ddd;
    border-top: none;
    background-color: #fff;
    max-width: 400px;
}

.mc-ac__result,
.mc-ac__status {
    padding: 6px 8px;
}

.mc-ac__result {
    cursor: pointer;
}

.mc-ac__result:hover {
    background-color: #f5f5f5;
}

.mc-ac__status {
    font-size: 13px;
    font-style: italic;
}

.mc-ac--hidden {
    display: none;
}

/* ------------------------------------------- and NOTHING is added, measured */

/*
 * ⭐ SEARCH-SPEC (b) SAID THIS DESIGN NEEDS ONE ADDITIVE LINE IN `custom_css` POST
 * 362, AND IT NEEDS NONE. The reasoning was that post 362 styles
 * `.elementor-widget-facetwp`, that Elementor stamps `elementor-widget-<name>` on
 * every wrapper, and that the four replacements would therefore fall out of that
 * rule. The first two are true. The third does not follow, because
 * `.elementor-widget-facetwp` ALREADY MATCHES NOTHING: the class Elementor actually
 * stamps for the old widget is `elementor-widget-facetwp-facet`, and a class
 * selector matches the whole token, not a prefix.
 *
 * Measured 7 Sept 2026 by running all 40 of post 362's selectors through
 * `document.querySelectorAll` in a real browser on both pages
 * (`<ts>-tools/match-362.gen.js`, results in `<ts>-before/sel362-*.json`):
 * `.elementor-widget-facetwp` -> **0 elements** on `/find-your-cause/` and **0** on
 * `/`. So does `.elementor-widget-mcmc-search`. Both are dead today and adding a
 * third dead selector beside them would have changed nothing and looked like it did.
 *
 * What actually gives the wrappers their 5px rhythm is the same rule's OTHER
 * selectors — `.mcmc-search`, `.mcmc-facet-btn` — which are `_css_classes` values on
 * the Elementor wrapper, and `scripts/templates/swap-facet-widgets.php` copies
 * `_css_classes` across verbatim. That is why post 362 keeps working with no edit.
 *
 * Of post 362's 40 selectors, 18 match on the directory and 24 on HOME. Every one of
 * them is satisfied by the four widgets' markup or by an element neither this seat
 * nor FacetWP owns (`.team-logos-grid` and `.team-logo img` are mcmc-core's logos
 * bar; `.mcmc-results`, `a[href*="story_flag"]` and `.player-video` are the theme's).
 * The dead 22/16 include `.mcmc-facet-group`, `.mcmc-uniform-width`,
 * `.mcmc-results-title *` and `.mcmc-search .facetwp-search` — that last one because
 * FacetWP's autocomplete input has always been `.facetwp-autocomplete`, so the rule
 * has never fired and the new markup does not resurrect it.
 */
