/* APED — the landing loader's new exit. * * The loader itself is UNTOUCHED: its intro, its ring, its percentage and * "Loading a vault of APES" are the mirror's own component and play exactly as * they did. Only the way it LEAVES changes, and only these two classes do it. * * How it used to leave (measured in site/assets/index.dc7c478f.css): the section * is a Vue `` over * a v-show, so when `maestro.showLoader` goes false Vue puts `loader-leave-active` * on `section.site-loader` and two keyframe animations run for 1.1 s — one on the * section, one on `.site-loader__inner` — and then the node is display:none. * * Now: the instant that class appears, `html.aped-loader-outro` cancels BOTH * animations and pins the loader at full opacity, the outro canvas is mounted * over it, and only when the canvas has painted one opaque frame does * `html.aped-loader-gone` take the loader off the screen. Neither class outlives * the outro — both are removed in onDone, by which time Vue's own 1.1 s leave is * long finished and its v-show holds display:none on its own. Nothing here is a * node, nothing is measured, and the bundle is not patched. * * Loaded only when content/fx.json has `transition.enabled` and * `transition.loaderOutro`; with either off the build writes neither this file's * nor loader-outro.js's