I get an error when loading scripts from a CDN because there is no hash set to the CDN Url. This could be fixed by giving more options to the scripts-array in the config:
Additionally this would add support for
asyncanddeferattributes
const config = {
scripts: [
{
src: "https://cdnjs.cloudflare.com/ajax/libs/featherlight/1.7.13/featherlight.min.js",
integrity: "sha256-/SEQTcl9tvyYDA8SuhV/PMn92shN3kNn8C9vnbBcE9Y=",
crossorigin: "anonymous",
async: true
},
"../js/theme.js",
]
};
yes
no error in the console
(Write what you thought would happen.)
Error in the console:
Refused to execute inline event handler because it violates the following Content Security Policy directive: "script-src https:". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution.
(Write what happened. Add screenshots, if applicable.)
@muuvmuuv I can't reproduce the issue using your example scripts (they all load as expected), but this is still a good feature to have.
@endiliey can I claim this? I think a simple check of if source is an Object, and simply spreading the object key/values as attributes would be sufficient, unless you would prefer whitelisting only the valid script tag attributes.
this.props.config.scripts.map(source => {
if (source instanceof Object) {
return <script type="text/javascript" key={source.src} {...source} />;
}
return <script type="text/javascript" key={source} src={source} />;
});
@helloworld it's yours!
I've added an "issue-claimed" label so that others will know not to start work on the issue. If you change your mind about the issue, no worries! Just let me know so that I can remove the label and free it up for someone else to claim.
I'll check in with you periodically so that we can keep the task updated with the progress.
@helloworld maybe it is just a problem of my local running environment. But yes would anyway a good feature. I鈥榤 looking forward to see this in the next updates
Sent with GitHawk
@helloworld still working on this ?
@wszgxa sure 馃憤. Send a PR in
@wszgxa it's yours!
I've added an "issue: claimed" label so that others will know not to start work on the issue. If you change your mind about the issue, no worries! Just let me know so that I can remove the label and free it up for someone else to claim.
I'll check in with you periodically so that we can keep the task updated with the progress.
@endiliey This appears to be available again. Can I snag it? Should have some time this weekend.
@ravennasoftware, sure.
Send a PR in. Best asap so we can release 1.5 along with it
My bad. #937 should have closed this
Most helpful comment
@muuvmuuv I can't reproduce the issue using your example scripts (they all load as expected), but this is still a good feature to have.
@endiliey can I claim this? I think a simple check of if source is an
Object, and simply spreading the object key/values as attributes would be sufficient, unless you would prefer whitelisting only the validscripttag attributes.