Skip to content

Meeting Notes 2018 07 10

Pieter Mees edited this page Jul 11, 2018 · 1 revision

Meeting Notes July 10, 2018

Summary

  • There was a discussion over whether the publisher “must” hide the ad on initialization or “may” show the ad while preloading.
    • Ryan will create an issue
  • There was discussion about versioning
    • one option is to just let the ad play and have the player take no action.
      • One problem is that the SIVIC ad might want to send messages and those messages will not be understood.
    • one option is to error out.
      • This means that some ads will error out when they might not need to.
    • Another option is to have a list of capabilities
    • One option is to have a vast parameter that gives min and max versions the ad supports. If the player is not compatible it would pre-emptively error out.

current version of ad start workflow (section 6 still hasn't been updated):

How to Handle Ad Loading

The player should follow this workflow for loading an ad:

  1. The player must creates an iframe element for the SIVIC ad.

    • The player iframe must start out hidden. The iframe should be capable of loading DOM.
  2. The player begins listening to the “message” event from the iframe following the SIVIC protocol. See reference to SIVIC protocol spec.

  3. The player sets the src element of the iframe to the url provided by the ad’s VAST InteractiveCreativeFile element.

    • The player should assume this will be a cross domain iframe.
    • The player should set the iframe up in a way that allows asset loading.
  4. The player waits until it receives “ready” from the ad before sending any messages to the ad.

    • The ready callback should have two key value parameters representing min and max version supported. For example min 7 and max 7 would mean only version 7 would be supported.
  5. The player responds

    • If the version is accepted, the player responds with “onReady” with the version it will use.
    • If the version is rejected, the player responds with an “error” message. This error will follow the standard error workflow (see How to Handle Ad End and Unload).
  6. When the ad is ready to render the player should overlay the ad over the player.

    • The ad could be made visible before it replies with handshakeVersion.
    • The ad should be visible when or before the first video frame is displayed.
    • The iframe should be attached to the DOM by the player.
    • The iframe should be the same size as the video element and overlay it entirely.
Clone this wiki locally