The plugin gets warning on Content-Security-Policy when loaded

[gaohoward]

Here is the console log screen

[gaohoward]

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy-Report-Only

[lavocatt]

Thanks Howard for reporting this issue. Do we know if that's related to the SPP or is that on the console by default?
A followup question is, is this issue related to the development environment?
Does the issue also occurs when running the console in standalone (without having to start the node process in the terminal)?
This would be valuable information to know to assessing the severity and if we can act onto something to fix the problem ourselves or if we need to report that back to the dynamic plugin sdk folks.