-
-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove use of innerHtml #621
Comments
If you're not against introducing a sanitizer (like DOMPurify), you could change this from and have the linter explicitly allow innerHTML as long as it's used in combination with dompurify. |
I have no problem adding DOMPurify to the ZAP domain - it could definitely prove useful. We're trying to limit what we include on the target domain, but that doesnt apply in this case. |
if I were to add dompurify as a dependency in package.json - do you have a build step to move a copy to |
Ah, I did not see you self-assigned. Nevermind then :-) I'll modify #620 to have the linter accept dompurify as an exception |
Yes, the HUD runtime JS is delivered by ZAP so we need it there. |
Which ones are copied are tracked here: Lines 96 to 106 in c1839b1
|
Part of fix for zaproxy#621 Signed-off-by: Simon Bennetts <[email protected]>
Re #620
The text was updated successfully, but these errors were encountered: