Eos Scripts teases not playing on Chrome
Posted: Thu Feb 14, 2019 6:37 am
I have a problem with the new HTML5 viewer not working on Chrome.
When I open a tease all I get is black screen with no loading. Tried disabling all extension and the problem is still there. And they work fine on Firefox.
Upon checking page inspection for a tease page I get the following:
And checking https://eosscript.com/
When I open a tease all I get is black screen with no loading. Tried disabling all extension and the problem is still there. And they work fine on Firefox.
Upon checking page inspection for a tease page I get the following:
Code: Select all
Active resource loading counts reached a per-frame limit while the tab was in background. Network requests will be delayed until a previous loading finishes, or the tab is brought to the foreground. See https://www.chromestatus.com/feature/5527160148197376 for more detailsCode: Select all
Refused to display 'https://eosscript.com/?host' because it has not opted-into the following policy required by its embedder: 'default-src 'none'; script-src https://eosscript.com; style-src https://eosscript.com; img-src https://eosscript.com https://media.milovana.com blob:; media-src https://eosscript.com https://media.milovana.com blob:; connect-src https://eosscript.com https://media.milovana.com https://sentry.io blob:; font-src https://eosscript.com; block-all-mixed-content'.Code: Select all
index.js:54 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://eosscript.com 'nonce-27FF92EC6A8020419065903E04650D6C' https://gc.kis.v2.scr.kaspersky-labs.com wss://gc.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution.Code: Select all
velocity.es5.js:2589 Refused to create a worker from 'blob:https://eosscript.com/59a88fb8-86f9-44e2-accf-16e6f4dc9964' because it violates the following Content Security Policy directive: "child-src https://gc.kis.v2.scr.kaspersky-labs.com wss://gc.kis.v2.scr.kaspersky-labs.com". Note that 'worker-src' was not explicitly set, so 'child-src' is used as a fallback.Code: Select all
index.js:4416 malformed rpc response from parent, no result or error given. id=0