PixiJS Ticker vs Page Visibility: Should the Ticker Auto‑Pause?

Integration Boundary: PixiJS Ticker and Page Visibility API

Goal: Determine whether PixiJS should automatically pause its internal ticker when the page becomes hidden, to avoid unnecessary GPU and CPU usage while maintaining animation continuity when the tab is restored.

Constraints: The ticker currently delegates to requestAnimationFrame, and developers often mix it with manual loops or visibility change handling. Automatic pausing may cause animation jumps if the developer also manages updates externally.

Uncertainty: Does the PixiJS community prefer built‑in pause behavior, or should the responsibility remain explicit to developers? How does this affect performance on mobile browsers with aggressive throttling?

Specific Questions

• What are the observable differences in frame timing and resource consumption when the PixiJS ticker auto‑pauses versus when it continues running during a hidden tab?
• How does automatic pausing interact with common patterns of manual update loops (e.g., setInterval or custom tickers) that developers might still employ?
• Should the PixiJS API expose a configurable option to enable or disable auto‑pause on visibility change, and what would be the default recommendation?