(function(){ "use strict"; try { if (window.self !== window.top) return; } catch (e) { return; } /* iframes (admin Mobile preview) are not ours */ try { var W = window; if (W.__wedHydrationWatchdog) return; W.__wedHydrationWatchdog = 1; /* DEV BAIL-OUT -- same predicate as isDevHost() in app/components/StaleBuildGuard.tsx. "next dev" compiles route chunks ON DEMAND, so a cold /admin/ routinely leaves several async scripts pending for 30-60s+ while Turbopack works; every other guard in this repo bails on dev and so must this one, or it drops a recovery panel over the owner's own localhost during ordinary work and trains him to dismiss it on sight. NOTE: gating on the build string instead does NOT work -- next.config.ts sets NEXT_PUBLIC_BUILD_ID unconditionally, including for "next dev", so BUILD below is a real bYYYYMMDDHHMMSS value on localhost and would never read "dev". */ var HOST = String(location.hostname || "").toLowerCase(); if (HOST === "localhost" || HOST === "127.0.0.1" || HOST === "::1" || HOST.slice(-6) === ".local" || /^10\./.test(HOST) || /^192\.168\./.test(HOST) || /^172\.(1[6-9]|2\d|3[01])\./.test(HOST)) return; var TICK = 1000; /* poll cadence */ var MIN_TOTAL_MS = 20000; /* absolute floor of VISIBLE time, measured from head parse */ var AFTER_COMPLETE_MS = 10000; /* ...and this much visible time AFTER the load actually completed */ /* (No "never completed" belt on purpose -- see the long note at the fire condition below. A page the browser is still fetching for has proved nothing about React, and firing there harms the slowest connections most.) */ var QUIET_TICKS = 5; /* consecutive ticks with NO new resource before the page is a candidate */ var MAX_FAILS = 5; /* tolerated thrown ticks before we give up (never on the first one) */ var BUILD = "b20260809151330"; var KEY = "wed_hydration_fail"; var visibleMs = 0; var completeAt = -1; /* visibleMs at the moment readyState FIRST became "complete" */ var lastRes = 0; /* resource-timing entries counted so far */ var quiet = 0; /* consecutive ticks that added no new resource */ var fails = 0; var last = Date.now(); var panel = null; var wroteCrumb = false; var iv = 0; function stop() { if (iv) { try { clearInterval(iv); } catch (e) {} iv = 0; } } function arm() { if (!iv) { last = Date.now(); try { iv = setInterval(tick, TICK); } catch (e) { iv = 0; } } } /* PROOF OF LIFE, READ TWO WAYS. app/components/HydrationWatchdog.tsx writes both a window property and an attribute on . The population this feature targets is, by its own evidence, browsers hardened to the point that History is frozen -- a sealed or frozen window makes the property assignment throw (that module is strict mode) and the catch eats it. The attribute survives that. Without this second reading, a page that hydrated perfectly would be told it never booted, and unlike the slow-load case that false positive does NOT self-heal. */ function hydrated() { try { if (W.__wedHydrated) return true; } catch (e) {} try { var de = document.documentElement; if (de && de.getAttribute && de.getAttribute("data-wed-hydrated")) return true; } catch (e) {} return false; } /* How many sub-resources have FINISHED. A PerformanceResourceTiming entry is only added once a resource completes, so a RISING count means "this page is actively downloading", which is the entire difference between a bad mobile connection and a dead page. Returns -1 when the API is missing; that is "no information", and we then fall back to the clock alone rather than treating silence as proof of death. */ function resourceCount() { try { if (W.performance && W.performance.getEntriesByType) { return W.performance.getEntriesByType("resource").length; } } catch (e) {} return -1; } function hide() { if (panel) { try { if (panel.parentNode) panel.parentNode.removeChild(panel); } catch (e) {} panel = null; } } /* React came up after all -- pretend we were never here. */ function standDown() { stop(); hide(); if (wroteCrumb) { /* Only ever delete a crumb WE wrote in this page context: an older crumb from a previous failed load still has to reach the Error Inbox via FreezeWatch. */ try { localStorage.removeItem(KEY); } catch (e) {} wroteCrumb = false; } } /* Targets are audited; see the note above HYDRATION_WATCHDOG_JS in app/layout.tsx. */ function signInPath() { var h = String(location.hostname || "").toLowerCase(); var p = String(location.pathname || "/"); /* Already on the sign-in page: Reload is the only thing left to offer, so no button. Tested BEFORE the /admin branch, which used to match /admin-login too and sent a stuck user to the page they were already stuck on. */ if (p === "/admin-login" || p.indexOf("/admin-login/") === 0) return ""; if (p === "/admin" || p.indexOf("/admin/") === 0) return h.indexOf("admin.") === 0 ? "/" : "/admin-login/"; /* /portals IS the Manager Portal, and /editor/ resolves through /portals/login/ to the same place -- so both land on the one manager page that really prerenders. */ if (p === "/manager" || p.indexOf("/manager/") === 0) return "/manager/signin/"; if (p === "/portals" || p.indexOf("/portals/") === 0) return "/manager/signin/"; if (p === "/editor" || p.indexOf("/editor/") === 0) return "/manager/signin/"; /* Studio dashboard -> the prerendered LoginScreen at "/". */ if (p === "/dashboard" || p.indexOf("/dashboard/") === 0) return "/"; /* Everything else -- /partner, /seller, and every PUBLIC page (an invitation, a gallery, a portfolio, a partner subdomain) -- gets no sign-in button. Public visitors have no account to sign in to, and partners have no page that survives a dead bundle. Falling through to "/" would have handed a partner's walk-in customer a studio owner's sign-in screen. */ return ""; } /* A guaranteed cache MISS for the "clear cache" reload, keeping any existing query and hash. Built by hand (no RegExp, no URL) so it cannot itself throw. */ function bustedUrl() { var s = String(location.search || ""); var raw = (s.charAt(0) === "?" ? s.slice(1) : s).split("&"); var keep = []; for (var i = 0; i < raw.length; i++) { if (raw[i] && raw[i].slice(0, 4) !== "_hw=") keep.push(raw[i]); } keep.push("_hw=" + Date.now()); return location.pathname + "?" + keep.join("&") + (location.hash || ""); } function css(el, text) { try { el.style.cssText = text; } catch (e) {} return el; } /* Everything is styled INLINE: if the bundle never ran, globals.css may not have loaded either, so a class name would buy us an unstyled pile of text. */ function makeBtn(label, primary, fn) { var b = document.createElement("button"); b.type = "button"; b.textContent = label; css(b, "flex:1 1 44%;min-width:132px;min-height:44px;box-sizing:border-box;padding:10px 12px;border-radius:10px;font-size:14px;line-height:1.25;cursor:pointer;font-family:inherit;" + (primary ? "border:none;background:#0A7CFF;color:#ffffff;font-weight:700;" : "border:1px solid #cbd5e1;background:#ffffff;color:#475569;font-weight:600;")); b.onclick = fn; return b; } function reloadNow() { try { location.reload(); } catch (e) { try { location.href = location.pathname; } catch (e2) {} } } /* Unregister every service worker + empty every Cache Storage bucket for this origin, then reload onto a cache-busted URL. Same teardown StaleBuildGuard does, written without async/await and with a 4s deadline so a wedged storage API can never leave the owner staring at "Clearing...". */ function clearAndReload(btn) { try { btn.disabled = true; btn.textContent = "Clearing..."; } catch (e) {} var went = false; function go() { if (went) return; went = true; try { location.replace(bustedUrl()); } catch (e) { reloadNow(); } } try { setTimeout(go, 4000); } catch (e) {} var jobs = []; try { if (navigator.serviceWorker && navigator.serviceWorker.getRegistrations) { jobs.push(navigator.serviceWorker.getRegistrations().then(function (rs) { var outs = []; for (var i = 0; i < rs.length; i++) { try { outs.push(rs[i].unregister().then(null, function () { return false; })); } catch (e) {} } return Promise.all(outs); }, function () { return false; })); } } catch (e) {} try { if (W.caches && W.caches.keys) { jobs.push(W.caches.keys().then(function (ks) { var outs = []; for (var i = 0; i < ks.length; i++) { outs.push(W.caches["delete"](ks[i]).then(null, function () { return false; })); } return Promise.all(outs); }, function () { return false; })); } } catch (e) {} try { Promise.all(jobs).then(go, go); } catch (e) { go(); } } /* Plain English for a non-technical reader. No jargon, no error codes, no blame. AUDIENCE NOTE: this root layout wraps the PUBLIC pages too -- invitations, galleries, portfolios, every partner subdomain -- so this text is read by couples and walk-in customers as often as by staff. It therefore says nothing about accounts (they have none) and invents no fear to then reassure. NON-BLOCKING ON PURPOSE: a bottom card with no scrim, matching StaleBuildGuard. The old full-viewport modal ate every click on a page that was merely slow and was about to come alive; on a page that is genuinely dead there is nothing behind it to click anyway, so the scrim bought us nothing and cost us that. */ function show() { var root = document.documentElement; if (panel || !root) return; var wrap = document.createElement("div"); wrap.setAttribute("role", "status"); wrap.setAttribute("aria-label", "This page did not finish loading"); /* pointer-events:none on the shell + auto on the card = nothing outside the card is swallowed. */ css(wrap, "position:fixed;left:0;right:0;bottom:0;z-index:2147483600;display:flex;justify-content:center;padding:12px;box-sizing:border-box;pointer-events:none;font-family:system-ui,-apple-system,'Segoe UI',Roboto,Arial,sans-serif;"); var card = document.createElement("div"); css(card, "pointer-events:auto;box-sizing:border-box;width:100%;max-width:420px;max-height:80vh;overflow:auto;background:#ffffff;color:#0f172a;border:1px solid #e2e8f0;border-radius:14px;padding:16px 18px;box-shadow:0 -8px 30px rgba(15,23,42,0.20);text-align:left;"); var head = document.createElement("div"); head.textContent = "This page didn't finish loading"; css(head, "font-size:16px;font-weight:700;margin:0 0 6px;color:#0f172a;"); var body = document.createElement("div"); body.textContent = "Something on this device stopped the page from starting. Nothing you were doing was lost. Try these:"; css(body, "font-size:13.5px;line-height:1.55;color:#475569;margin:0 0 12px;"); var row = document.createElement("div"); css(row, "display:flex;flex-wrap:wrap;gap:8px;"); row.appendChild(makeBtn("Reload", true, reloadNow)); /* OFFLINE: never offer to wipe the caches. The service worker may be the only thing still serving this app -- for a studio owner running the installed PWA at a venue with no signal, clearing it means the reload can be satisfied neither from cache nor from the network, and they land on the browser's "No internet" page with an app that is now empty. Strictly worse than the spinner they started with. */ var offline = false; try { offline = (navigator.onLine === false); } catch (e) {} if (!offline) { var clearBtn = makeBtn("Clear cache and reload", false, function () { clearAndReload(clearBtn); }); row.appendChild(clearBtn); } /* Only when there is a destination that really prerenders a sign-in form. */ var dest = signInPath(); if (dest) { row.appendChild(makeBtn("Go to sign-in", false, function () { try { location.href = dest; } catch (e) { reloadNow(); } })); } card.appendChild(head); card.appendChild(body); card.appendChild(row); if (offline) { var offNote = document.createElement("div"); offNote.textContent = "You appear to be offline. Reconnect, then reload."; css(offNote, "font-size:12.5px;line-height:1.5;color:#94a3b8;margin:10px 0 0;"); card.appendChild(offNote); } var dismiss = document.createElement("button"); dismiss.type = "button"; dismiss.textContent = "Hide this message"; css(dismiss, "display:block;margin:12px auto 0;border:none;background:none;color:#94a3b8;font-size:12.5px;font-family:inherit;text-decoration:underline;cursor:pointer;padding:4px;"); /* Deliberately stop + hide only, NOT a crumb delete. The crumb is safe either way: FreezeWatch ignores any crumb written by its own document, so if the page recovers after a dismiss nothing false is filed -- while if the page really is dead, the record of it survives for the next healthy load to report. Deleting here would throw away the only evidence of a genuine failure the user shrugged off. */ dismiss.onclick = function () { stop(); hide(); }; card.appendChild(dismiss); wrap.appendChild(card); /* Appended to , not : is what React hydrates, and an extra child there during hydration can surface as a recoverable hydration error, forcing a full client re-render -- turning a slow-but-recovering page into a slower one. It is fixed-position, so it renders identically. */ root.appendChild(wrap); panel = wrap; } /* The breadcrumb. A page that cannot boot cannot talk to Firestore, so we leave the facts on disk and let the next HEALTHY load file them (FreezeWatch reads this and reports it as [hydration-fail]). n counts repeats inside a day so a recurring failure is visible as one row that says "3 times", not three rows. */ function crumb() { try { var prev = null; try { prev = JSON.parse(localStorage.getItem(KEY) || "null"); } catch (e) {} var fresh = prev && prev.t && (Date.now() - prev.t) < 86400000; var n = (fresh && typeof prev.n === "number" && prev.n > 0) ? prev.n + 1 : 1; localStorage.setItem(KEY, JSON.stringify({ t: Date.now(), path: String(location.pathname + location.search).slice(0, 200), host: location.hostname, v: BUILD, rs: document.readyState, secs: Math.round(visibleMs / 1000), n: n })); wroteCrumb = true; } catch (e) {} } function tick() { try { var now = Date.now(); var delta = now - last; last = now; if (hydrated()) { standDown(); return; } /* React is alive -- done */ if (document.visibilityState && document.visibilityState !== "visible") return; /* not being looked at */ if (delta > TICK * 3) return; /* throttled / slept / just refocused */ visibleMs += delta; if (panel) { /* React can sweep unmatched nodes while hydrating; if the page is still dead, put the escape hatch back. */ if (panel.isConnected === false && document.documentElement) { try { document.documentElement.appendChild(panel); } catch (e) {} } return; } /* (1) IS THE NETWORK STILL DELIVERING? While new resources keep landing, this page is downloading, not dead -- /admin alone pulls ~19 async chunks and async scripts delay the load event, so on a congested link readyState legitimately stays "interactive" for 30-60s. Firing there would tell a user with a working (slow) connection that their page is broken, and both remedies on offer would throw away the partial download and restart it. */ var n = resourceCount(); if (n >= 0 && n > lastRes) { lastRes = n; quiet = 0; } else if (quiet < QUIET_TICKS) { quiet++; } /* (2) LATCH THE CLOCK TO LOAD COMPLETION. Counting from head parse meant that on any load slower than the 20s floor React got under a second of grace before the panel dropped -- and hydrating the admin tree on a low-end Android takes several. We now note when the load actually finished and give React a real window after THAT. */ if (completeAt < 0 && document.readyState === "complete") completeAt = visibleMs; if (quiet < QUIET_TICKS) return; /* still downloading -> not dead */ /* (3) 2026-07-25 -- THE LOAD MUST HAVE FINISHED. Full stop, no backstop. An earlier revision also fired after a fixed "never completed" deadline while document.readyState was still "loading". Three separate reviews proved that is a FALSE-POSITIVE GENERATOR and cannot be rescued by tuning: PerformanceResourceTiming entries only exist on COMPLETION, so an HTTP/2 download where all 19 chunks land together -- the NORMAL shape -- looks identical to a dead network right up until it finishes, as does any short signal dropout at a wedding venue. Simulating the real emitted script showed the panel dropping at 120s over a page that went on to load at 158s and hydrate fine at 163s. Losing that path costs us nothing we can actually detect: every failure mode this watchdog exists for -- an uncaught throw during boot (the live "Cannot assign to read only property 'pushState'" row), a 404'd chunk, a failed RSC fetch -- still fires the load event, so readyState DOES reach "complete" and the normal path below catches it. The one case genuinely given up is "a resource hangs forever", and that page is still downloading as far as the browser is concerned; telling its owner it is broken, and offering a button that discards the partial download and restarts it, would harm exactly the users on the worst connections. A missed report beats a false alarm. */ if (completeAt < 0) return; if (visibleMs < MIN_TOTAL_MS) return; if ((visibleMs - completeAt) < AFTER_COMPLETE_MS) return; crumb(); show(); } catch (e) { /* Never disarm on a single bad tick. show() can race a being replaced (a global-error swap, an extension mutating the DOM -- extensions being the cited root cause), and permanently killing the escape hatch on the one page that needed it is a worse outcome than retrying next second. */ fails++; if (fails > MAX_FAILS) stop(); } } arm(); /* Navigating away must never leave a recovery panel flashing over a page on its way out. pagehide alone does NOT cover it: pagehide fires when the NEW document commits, so on the very connections that make this panel possible, a user who taps a link at t=19s is still sitting on the old document when the panel would appear. A capture-phase click on a real link is the earliest honest signal of "I am leaving". */ try { window.addEventListener("pagehide", function () { stop(); hide(); }); } catch (e) {} try { window.addEventListener("beforeunload", function () { stop(); hide(); }); } catch (e) {} try { document.addEventListener("click", function (ev) { try { var t = ev.target; while (t && t.nodeName !== "A") t = t.parentNode; if (!t || !t.getAttribute) return; var href = t.getAttribute("href"); /* An in-page anchor is not a departure. */ if (href && href.charAt(0) !== "#") { stop(); hide(); } } catch (e) {} }, true); } catch (e) {} /* BFCACHE RESTORE. pagehide also fires when the document enters the back/forward cache, and stop() has no counterpart -- so without this, the sequence "open /admin/, it hangs on the prerendered spinner, tap Back, tap Forward" restores that same never-hydrated document with the watchdog permanently disarmed: the original bug, unchanged. iOS Safari also fires pagehide on app backgrounding in several versions. */ try { window.addEventListener("pageshow", function (ev) { try { if (ev && ev.persisted && !hydrated()) arm(); } catch (e2) {} }); } catch (e) {} } catch (e) { /* swallow: a broken watchdog must not break a working page */ } })();