To get started, install the Screenly CLI.
Add Engadget as an asset
$ screenly asset add https://www.engadget.com Engadget +----------------------------+-------------+------+--------+ | Id | Title | Type | Status | +----------------------------+-------------+------+--------+ | XXXXXXXXXXXXXXXXXXXXXXXXXX | Engadget | N/A | none | +----------------------------+-------------+------+--------+
Let's store the Asset ID for later
$ export ASSSET_ID=XXXXXXXXXXXXXXXXXXXXXXXXXX
Alternatively, we can use the nifity
--jsonoption in the CLI and pipe it to
jqto just get the Asset ID:
$ screenly asset list --json | jq -r '. | select (.title|test("Engadget")) | .id' XXXXXXXXXXXXXXXXXXXXXXXXXX
yahoo-cookies-consent-closing.js does just that, so let's apply it to our asset using the CLI.
Apply our Yahoo cookie consent closer to the Engadget asset
That's it! When the asset now loads on your screen, the above snippet will run automatically and close the cookie consent dialogue.
- Your script should be idempotent as it can run multiple times.
- Your script should execute with an interval or await when a specific element appears on the page. There is no guarantee that the page is fully loaded when the injector runs the script.
- Screenly player persists cookies set for a slide until the player reboots or playlist changes. You can check if you have already set a cookie to optimize your script.
- If your page includes redirects, the player will execute the injection script on each page.
- Sign in to Screenly via cookies
- Sign in to Tableau via cookies
- Sign in to Power BI via cookies
- Sign in to Power BI via credentials
- Sign in to Ship Hero via credentials
- Sign in to Magento Dashboard via credentials
- Sign in to Domo Dashboard via credentials
- Sign in to Domo Dashboard via access code
- Yahoo cookies consent closing
- Ez-cookie cookies consent closing
- Sign in to Jenkins via credentials
- Sign in to Shopify via credentials
- Sign in to Nagios via credentials
- Sign in to Cyfe via credentials