-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cap skip timer to video duration #701
Comments
@leichter - for selfie campaigns, lets change it to default at 5 seconds, ASAP. |
@leichter Is this something I should do on the front end? |
@sqmunson changing the default to 5 seconds ASAP is something I will do via policy change - aka all selfie users will now have 5 as the default value for |
I'm currently setting |
That last comment is for Selfie only. I'll have to take a look at Campaign Manager to determine side effects there. |
@leichter In the campaign manager |
@sqmunson if a user can set the |
@leichter So if a Selfie campaign/card is created and does not yet have a video, and therefore no duration to check, |
@sqmunson if a card does not yet have a video, the We can check the duration on VAST tags, so they are treated the same as other valid videos. |
The
data.skip
property is always being set to30
for selfie users' cards. However, if a selfie user's card has a video shorter than 30 seconds, the end user viewing the card will be stuck watching an ended video until the skip timer completes.Since we're fetching and setting the video duration on the backend, we can have the backend cap the skip timer to the video duration; so if the
data.skip
property is a number greater thandata.duration
, it'll setdata.skip
todata.duration
. This would mean that it'd be impossible for anyone to set a skip greater than the video duration, which I don't know if we want to make possible (to force users to read text on card or something).cc @howardengelhart, @sqmunson
The text was updated successfully, but these errors were encountered: