5 years ago
Web: 8.17.3
- Fixed an issue to work around a bug in the Google IMA SDK affecting Android Chrome 84 only where unplayable linear ad MIME types were being erroneously selected.
on('meta') and on('metadataCueParsed') events.setFloating(), which starts and stops the player from floating, and getFloating(), which returns the current floating status.mode, which defaults to notVisible, which is current behavior for floating when the original container would be out of view. always can be used to start floating and never stop unless updated with the API, and never can be used to not float, unless updated by API.adRequest event has been changed to fire each time we make ad request to IMA SDK. adLoaded event, which fires when IMA's LOADED event fires.playlistItem event to update an ad schedule. By the time that event fires, the schedule for the playlist item has already been created, so the change does not have an effect. Please use setPlaylistItemCallback to properly update the ad schedule.setCurrentAudioTrack is called.on('meta') and on('metadataCueParsed') methods based on in-band emsg timed metadata.jwpseg macro from within VAST tags contained within a wrapper.amp-jwplayer component.playlistIndex, which enables a playlist to be loaded and start playback from any item within it, not just the first. The default of this option is a 0 index.video-seconds-played trigger listed for configuration in amp-video-analytics does not work properly in this release. This will be fixed in a future release. All other triggers listed should operate as expected.