Specify player resize limitations at initializing

[ryanthompson591]

Freewheel indicated that some errors regarding resizing shouldn't necessarily stop playback. To what extent should prefer adding player capabilities?

--- entire conversation below --- Regarding error in 1000 block: Traditionally error event is the last ad breath. In other words - errors imply ad destruction.

Are, for example errors 1007 and 1008 imply that ad becomes non-functional? Or these (and other) errors are designed to notify ad about limitations.

If former - is player obligated to stop video playback?

Player environment limitations do not organically fall into error category. If there is a need for ad to receive feedback, either we need to introduce new notifications category or, better, limitations should be communicated by player to ad at bootstrapping/handshake/initialization.

FreeWheel TV 12:25 PM Mar 22 Shouldn't these be defined in the VAST 4.1 specification instead?

Pieter Mees 3:30 PM Mar 22 Also, currently in VAST all VPAID errors are coerced back into a single 901 error code. This means a lot of debugging information gets lost in VAST error pixels. Can we correct that?

[amitshetty]

I will check with Freewheel to clarify the question. Otherwise we will close since it isnt clear what the discussion is about to us.

[ryanthompson591]

I think this is now obsolete as we've made many changes to errors and SIVIC overall.