The Boros TCF stub implements the standard TCF v2 stub
-
Registers the
__tcfapiLocatorframe -
Stubs the
window.__tcfapiresponding immediately to the commandspingSee PingReturn in the stubbed __tcfapipendingreturns the pending calls accumulated while callingwindow.__tcfapicommandsonReadyreturns the optional registeredonReadycallback
-
Initializes the cross-framee communication via
postMessagee, see usage details
Use it this way if you're generating your own initialization
Install
npm i @adv-ui/boros-tcf-stub --save
Register the Stub
import registerStub from '../main'
// do your magic
registerStub()
Register the Stub with an onReady callback
This allows creating additional commands that can have access to the Boros TCF API facade.
import registerStub from '../main'
const onReady = api => initializeCustomCommands(api)
registerStub({onReady})
The
onReadycallback will be called after Boros TCF initializes thewindow.__tcfapiand before processing any pending command in the stub's queue.
Remember that the Stub must be registered before any script depending on the TCF is loaded
Add it to the head tag
<script
src="https://c.dcdn.es/borostcf/stub/BorosTcfStub.pro.js"
async="false"
/>
This does not accept registering an
onReadycallback. Import theregisterStuband generate your own script if it's a need.
Boros TCF Stub is MIT licensed.