Hence proper CORS configuration is required on your ad-server in order for rmp-vast to be able to retrieve VAST tags. Rmp-vast uses JavaScript XMLHttpRequests to load VAST tags. It is fairly possible that rmp-vast would work in other environments but they are not officially supported.īack to documentation sections CORS requirements
#RADIANT MEDIA PLAYER EXAMPLE UPDATE#
See this blog post to help you update to WKWebView API. With the announcement of Apple in december 2019, to remove support for UIWebView API by end 2020, we only support WKWebView API for iOS apps built with Cordova, Ionic or WebView. API to build a fully fledged player on top of rmp-vastīack to documentation sections Supported environments Browsersĭesktop means Windows 7+, macOS 10.11+, Linux (latest LTS Ubuntu).Autoplay support (muted autoplay on iOS, Android, Desktop Chrome 66+ and Desktop Safari 11+).ViewableImpression, Universal Ad ID, AdServingId, Survey and Ad Categories.Audio Ads (MP3/M4A/HLS where natively supported) in HTML5 video.Tracking Events (tracking URLs must return an image - typically a 1px GIF/PNG/JPG).Linear creatives in HLS format on all supported devices (with hls.js) - BETA.Linear creatives in MP4/WebM progressive download.Parameters when creating a rmp-vast instance.Video ads from Google Ads network and rmp-vast.Rmp-vast is used and maintained by Radiant Media Player. Rmp-vast makes use of vast-client-js for fetching and parsing VAST XML resources. It is up to you to transpile/polyfill the library if needs be. Rmp-vast is written in ES2017 and does not include any polyfill or transpiling to ES5 for backward compatibility. VAST 2 and VAST 3 support is also provided. ) where both HTML5 video and JavaScript are available. It aims at implementing the IAB VAST 4.2 specification for web-based environments (e.g. A client-side JavaScript solution to load, parse and display VAST resources (advertising).
0 kommentar(er)
