WPIntell

Source evidence

problems with no-unsafe .js

No unsafe-inline · support · 2024-10-10T17:49:00+00:00

complaintsentiment
highseverity
0.96relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 35 rows with source links

14.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
fuzzy21 unresolved
I’m having problems getting this one to work: no-unsafe-inline-fix-style.min.js?ver=1.2.2:2 [Report Only] Refused to apply inline style because it violates the following Content Security Policy directive: “style-src https://pro.fontawesome.com ‘nonce-f729f65c7d6625f00e4266825df72b094d37e64c6e7ad38d8590bc6deab4c949’ ‘report-sample'”. Either the ‘unsafe-inline’ keyword, a hash (‘sha256-N0psPaXG96mUcdWtcusjcwUFwppzPflJqwG7HJYmREw=’), or a nonce (‘nonce-…’) is required to enable inline execution. Element.insertBefore @ no-unsafe-inline-fix-style.min.js?ver=1.2.2:2 (anonymous) @ 98c73cfb02.js:2 (anonymous) @ 98c73cfb02.js:2Understand this er I can see it in source with integrity=”sha256-3rZtO7fq9/9d7P…” crossorigin=”anonymous” nonce=”b6accd…” It’s whitelisted, I tried hash, rehash and even deleting and then white listing, but still not working. Please, post a link to the page with this issue It’s internal site, here is screenshot of source View post on imgur.com The script (no-unsafe-inline-fix-style.min.js) overrides some js primitive functions/methods trying to deal with a use of these functions in third libraries/scripts not csp compliant (but it cannot handle every situation, and this is one of the main problems that this plugin has to deal with, because the loaded node cannot be read and “captured” before it is sent to the browser). Please, visit the urls linked in the settings page to better understand the problem. What is happening here is that a third script is calling node.insertBefore() method to add a <style> element or an html element with a style=”…” attribute. Your browser is refusing to process this dom node, not the script. It is clear that here the nunil script fails to overwrite the method to load the inserted html in a csp compliant way. To understand what’s happening, I should see the page, or you can simply disable this feature by disabling the “fix_settribute_style” option, in the settings tab. Then you should get errors that will address directly to the code calling the node.insertBefore() method.

Comments

3 shown
Giuseppe 2024-10-12T09:42:00+00:00

Please, post a link to the page with this issue

fuzzy21 2024-10-14T14:11:00+00:00

It’s internal site, here is screenshot of source View post on imgur.com

Giuseppe 2024-10-14T22:14:00+00:00

The script (no-unsafe-inline-fix-style.min.js) overrides some js primitive functions/methods trying to deal with a use of these functions in third libraries/scripts not csp compliant (but it cannot handle every situation, and this is one of the main problems that this plugin has to deal with, because the loaded node cannot be read and “captured” before it is sent to the browser). Please, visit the urls linked in the settings page to better understand the problem. What is happening here is that a third script is calling node.insertBefore() method to add a <style> element or an html element with a style=”…” attribute. Your browser is refusing to process this dom node, not the script. It is clear that here the nunil script fails to overwrite the method to load the inserted html in a csp compliant way. To understand what’s happening, I should see the page, or you can simply disable this feature by disabling the “fix_settribute_style” option, in the settings tab. Then you should get errors that will address directly to the code calling the node.insertBefore() method.