breaks" after a Stonly release * ---------------------------------------------------------------------------- * Stonly renders guides with auto-generated CSS-in-JS class names (the kind * that look like `Explanation__Canvas-sc-a1b2c3` or `SearchBar-styles__Wrap-sc-x9y8`). * Stonly has told us directly: those generated names are NOT guaranteed to stay * stable across releases — only classes that are static (hand-authored, no hash * suffix) are guaranteed to stick around. `.kb-guide` is the one confirmed-stable * hook we currently have (confirmed by Stonly's lead frontend engineer, Aug 2026). * * Everything below still targets the generated pattern via `[class*="..."]` * substring selectors, because that's the only way to reach those elements today. * That means every selector containing `-sc"` or `-styles__` in this file is a * KNOWN FRAGILE POINT that can silently stop matching after any Stonly release. * * When something visually breaks after a release: * 1. Open devtools on the guide, find the element that lost its styling. * 2. Compare its current class list to the `[class*="..."]` selector that * was supposed to match it in the CSS below. * 3. Update the selector's substring to match the new generated class name. * 4. Ask Stonly whether that element also has (or can get) a static class — * if so, prefer that going forward, the way `.kb-guide` was adopted. * * The JS below is wrapped in `safeRun()` so that if a selector stops matching, * that one feature just silently no-ops (with a single one-time console.warn * for whoever's debugging) instead of throwing and potentially breaking the * other unrelated features that share the same setInterval/DOMContentLoaded tick. * ============================================================================ */ window.__disableAnalytics = true; window.StonlyWidget.disableTargeting = true; window.StonlyWidget.disableTracking = true; // Runs fn and swallows any error so one broken selector can't take down the // other independent features running in the same tick. Warns once per label // (not on every tick) so a real break is diagnosable without flooding the console. const _lhWarnedOnce = new Set(); function safeRun(label, fn) { try { fn(); } catch (err) { if (!_lhWarnedOnce.has(label)) { _lhWarnedOnce.add(label); console.warn( '[Liebherr KB custom code] "' + label + '" failed — a Stonly-generated ' + 'class this code depends on may have changed. See the maintenance note ' + 'at the top of this