carusoapps

@missveronicatv this is what I see on Brave

1. Content Security Policy of your site blocks the use of ‘eval’ in JavaScript`
   1. The Content Security Policy (CSP) prevents the evaluation of arbitrary strings as JavaScript to make it more difficult for an attacker to inject unathorized code on your site.To solve this issue, avoid using <code class=” “>eval(), <code class=” “>new Function(), <code class=” “>setTimeout([string], …) and <code class=” “>setInterval([string], …) for evaluating strings.If you absolutely must: you can enable string evaluation by adding <code class=” “>unsafe-eval as an allowed source in a <code class=” “>script-src directive.⚠️ Allowing string evaluation comes at the risk of inline script injection.
   2. 1. 1 directive
         1. Source locationDirectiveStatusscript-srcblocked
   3. • Learn more: Content Security Policy – Eval
2. Incorrect use of <label for=”FORM_ELEMENT”></label>
   1. The label’s <code class=” “>for attribute doesn’t match any element <code class=” “>id. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.To fix this issue, make sure the label’s <code class=” “>for attribute references the correct <code class=” “>id of a form field.
   2. 1. 4 resources
         1. Violating nodeViolating nodeViolating nodeViolating node
   3. • Learn more: The label elements

• This reply was modified 8 months, 1 week ago by carusoapps.