ReadonlyadDispatched when the current ad break has completed: all of its ads played, were skipped, it hit its playout limit, or it had no ads. Carries the position at which primary content resumes.
ReadonlyadDispatched when an ad break has been entered — its ads may still be resolving. An ad break may contain one or more ads.
ReadonlyadDispatched when an ad has stopped playing for any reason such as ended, error, or skipped.
ReadonlyadDispatched when an ad has played through 100%. Will be dispatched before adCompleted.
ReadonlyadDispatched when an ad region has been entered.
ReadonlyadAn ad list or an individual ad failed to complete.
ReadonlyadDispatched when an ad has played through 25%.
ReadonlyadDispatched when an ad has played through 50%.
ReadonlyadDispatched when an ad has started playing.
ReadonlyadDispatched when the playhead approaches a midroll or postroll break — within the break's resolution/preload window — so its ad assets can be resolved and warmed ahead of entry. Fires once per break as it is approached (again after a seek back re-arms a replayable break). Prerolls are preloaded up front and do not emit this.
ReadonlyadDispatched when an ad has played through 75%.
ReadonlyadDispatched on each playback progress tick while an ad is active, carrying the elapsed and remaining time for both the current ad and the whole ad break. Applications should prefer this over deriving ad timing from the media element's duration.
ReadonlycurrentEmitted when the set of known ad breaks for the current media changes, for example when a live manifest reveals a new break.
Events dispatched by an AdController. These are provider-agnostic: an application listens once and receives the same events whether the ads originate from HLS Interstitials or DASH SCTE-35.