/* glow-v2.css - the pointer comet's layer.
 *
 * Three declarations do the work; everything else is here to stop the layer
 * from ever being anything other than paint. The behaviour is glow-v2.js, the
 * measurements it is built from are _build/GLOW-MEASUREMENTS.md, and the
 * markup is STRUCTURAL EDIT 39.
 *
 * WHY THE SELECTORS CARRY .bg
 *
 * Same reason bg-v2.css gives, and it is worth repeating because it is not
 * obvious: the rules this sheet has to sit alongside live in an inline <style>
 * in the BODY of the captured page (the .css-embed block after the bg-shape
 * divs). This file is linked from <head>, so it loses any same-specificity tie
 * on document order. Scoping to the .bg ancestor makes it (0,2,0) against the
 * source's (0,1,0) and it wins without !important. `.glow-v2` collides with
 * nothing in the Webflow bundle - checked - but the scope also documents where
 * the element is allowed to exist, which is the more useful property.
 *
 * Z-INDEX 1 IS COPIED FROM THE ORIGINAL, NOT PICKED
 *
 * §1 of the dossier measured everwonder.studio's scene wrapper at
 * `position:absolute; z-index:1; mix-blend-mode:lighten` inside the same
 * `.bg` (`position:fixed; inset:0; z-index:0`). That puts it above the base
 * gradient and the blurred dodge streaks (all z-index auto) and BELOW
 * `img.bg-noise`, which the Webflow bundle gives `z-index:2` and 30 %
 * `soft-light`. So the grain sits over the comet rather than under it - which
 * is how the reference frames were captured and therefore how the measured
 * #626AE7 was measured. Raising this layer above the noise would be a
 * different composite and a different colour.
 *
 * `.bg` itself is z-index:0 and stays that way, which is what keeps the whole
 * effect strictly BEHIND every piece of page content (§1: main.main-wrapper is
 * z-index:1, the nav is 100).
 *
 * MIX-BLEND-MODE: LIGHTEN, likewise measured. Over the graphite backdrop the
 * layer can only ever brighten; a dim tail whose blue channel is below the
 * backdrop's simply does not show, which is the behaviour the reference frames
 * have over the brighter lower half of the page.
 *
 * NO CANVAS IN THE MARKUP. The <canvas> is created by glow-v2.js and only when
 * the effect is actually going to run - not on touch, not under
 * prefers-reduced-motion. An empty div costs nothing; an idle canvas element
 * with a backing store is 8 MB of GPU memory for a device that will never see
 * a pointer.
 */

.bg .glow-v2 {
  position: absolute;
  inset: 0;
  z-index: 1;
  pointer-events: none;
  mix-blend-mode: lighten;
  contain: layout paint;
}

.bg .glow-v2 canvas {
  display: block;
  width: 100%;
  height: 100%;
}
