The google-ima.js surrogate should fire the correct events when
AdManager.start() is called, to emulate the ads playing and
finishing. It's also important that these events[1] are fired in the
right order. CONTENT_PAUSE_REQUESTED should fire around when the ads
are starting, and CONTENT_RESUME_REQUESTED around when the ads have
finished. Correcting this ordering fixes website that use the Video.js
the integration of IMA, for example metro.co.uk.
The google-ima.js surrogate should fire the correct events when AdManager.start() is called, to emulate the ads playing and finishing. It's also important that these events[1] are fired in the right order. CONTENT_PAUSE_REQUESTED should fire around when the ads are starting, and CONTENT_RESUME_REQUESTED around when the ads have finished. Correcting this ordering fixes website that use the Video.js the integration of IMA, for example metro.co.uk.
1 - https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side/reference/js/google.ima.AdEvent