/* static/css/stable_paint.css
 *
 * No backdrop blur anywhere in the portal.
 *
 * Every screen flickered: for one frame the page's top layers — the sticky top
 * bar, an open modal and its tint — vanished and came back. A screen recording
 * pinned it down: the flash lasts a single frame (~18 ms), covers the whole
 * viewport, happens with the mouse still, and focus stays put in whatever field
 * the user was typing in. That is not this app's JavaScript opening or closing
 * anything; it is Chrome (macOS especially) dropping a compositor layer for a
 * frame.
 *
 * The layers it drops are `backdrop-filter` ones. The top bar is sticky, blurred
 * and on every page, and the loading line inside it animates on every
 * background request (notification polls, reminders, searches) — so the blur
 * behind it is recomputed constantly, and each recompute is a chance for the
 * compositor to show a frame without it. Modals added a full-screen blurred
 * backdrop on top of that.
 *
 * One rule, loaded by every layout, rather than 80 class edits that the next
 * template would undo: `backdrop-filter` is off. Surfaces that were
 * see-through *because* they were frosted are made solid where they sit over
 * moving content (the sticky bars, in their templates); dim overlays keep their
 * tint. Do not add backdrop blur back — use a solid or slightly translucent
 * background instead.
 */
*, *::before, *::after {
  -webkit-backdrop-filter: none !important;
  backdrop-filter: none !important;
}

/* The Intelligence module's "liquid glass" cards were translucent over an
   aurora background and relied on a 40px blur to stay readable. Without the
   blur they use the solid fallback intel.css already defines for browsers
   that cannot blur. */
.intel-root .glass,
.intel-root .glass-2 {
  background: var(--glass-bg-solid, rgba(20, 22, 30, 0.96)) !important;
}
