Animation Component vs Asset‑Item Timeout: Coordinating Cancellation on Load Failure

Goal: When an <a-asset-item> triggers its timeout error event, any animation component attached to the same entity should be stopped so that its tick handler does not continue to run and waste render cycles.

Constraints: The animation component exposes only pause() and play() methods, lacks an explicit cancel or stop API, and does not reset internal timers when paused. Asset‑item timeouts cannot abort the underlying XHR/fetch request, leaving network traffic active after the error event. Removing an entity from the scene runs component remove callbacks but does not automatically cancel animations, so lingering tick handlers may persist unless manually cleaned up. Mixins that duplicate animation data do not share cancellation state, making coordinated timeout handling across mixed‑in instances unclear.

Specific questions:

• Does A‑Frame provide a built‑in way to pause or stop an animation automatically when an asset‑item timeout error event is emitted?
• Can a mixin‑based animation be collectively cancelled from a parent entity, or must each instance be managed individually?
• What is the recommended pattern for cleaning up animation tick handlers after a timeout without bypassing the framework’s lifecycle?