Treat a shader effect as a runtime dependency, not decoration alone. Before using one, verify the rendering technology, browser and device coverage, GPU and library requirements, resize behavior, reduced-motion and non-WebGL fallback, interaction with page content, cleanup behavior, and license. Use only examples with a working preview and item-specific implementation facts.
Runtime audit
Three exact published shader effects with different visual jobs were replayed through a fixed desktop, mobile, reduced-motion, forced non-WebGL, resize, interaction, and route-change procedure. Chromium, Firefox, and WebKit observations are reported separately from each catalog record's declared browser support. The audit exercises public preview adapters and metadata; it does not benchmark or expose protected source.
Reviewed: by vro.dev public preview and lifecycle audit.
Inline static SVG object study when the WebGL renderer is unavailable
Unmount procedure cancels animation, disconnects observers, removes listeners and canvas, disposes scene resources, and releases the context
Requires WebGL; higher-detail geometry and shadows are selected only for sufficiently large fine-pointer layouts. The audited Chromium preview also emitted non-fatal Three.js shadow-map deprecation and shader-precision warnings.
A full-bleed spectral light installation with original GLSL, responsive pressure, real motion control, keyboard interaction, capped rendering, and a static context fallback.
Runtime constraint: The host must provide a browser WebGL environment and retain the reviewed static or reduced-motion fallback for unsupported devices.
Runtime constraint: The host must provide a browser WebGL environment and retain the reviewed static or reduced-motion fallback for unsupported devices.
Runtime constraint: The host must provide a browser WebGL environment and retain the reviewed static or reduced-motion fallback for unsupported devices.
Method and limits
This is a functional public-preview audit, not a GPU benchmark, frame-time study, thermal test, or guarantee for every host layout. Device and browser declarations remain item metadata until tested in the target project. Re-test delivered source with representative content and hardware, preserve the fallback and cleanup contract, and profile the complete page before production use.