We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We might want to think about what happens, when the browser running a purified website is not supporting what DOMPurify needs.
Should we just return the original string? Or are we in a position to modify something?
The text was updated successfully, but these errors were encountered:
See #36
85de1e8
Added feature test and opt-out
That should do and tests pass. Any thoughts?
/* Feature check and untouched opt-out return */ if(typeof document.implementation.createHTMLDocument === 'undefined') { return dirty; }
Sorry, something went wrong.
Improved fixes for cure53#35 and cure53#36.
0d901ed
No branches or pull requests
We might want to think about what happens, when the browser running a purified website is not supporting what DOMPurify needs.
Should we just return the original string? Or are we in a position to modify something?
The text was updated successfully, but these errors were encountered: