We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Bustracker:
This app:
Since Avail supports it, I guess we don't really have a choice either. Shouldn't be that bad, the two possible pain points I foresee are:
The text was updated successfully, but these errors were encountered:
Quick research presents two options:
Sorry, something went wrong.
From the FAQ on html-react-parser:
html-react-parser
Is this XSS safe? No, this library is not XSS (cross-site scripting) safe. See #94. Does invalid HTML get sanitized? No, this library does not sanitize HTML. See #124, #125, and #141.
Is this XSS safe?
No, this library is not XSS (cross-site scripting) safe. See #94.
Does invalid HTML get sanitized?
No, this library does not sanitize HTML. See #124, #125, and #141.
However, possibly useful examples in the comments of one of those issues:
sanitize-html
DOMPurify
Add HTML message rendering support (#22)
046e3ff
Sanitize and render HTML in messages, as the avail bustracker does. Closes #21
benmelz
Successfully merging a pull request may close this issue.
Bustracker:

This app:

Since Avail supports it, I guess we don't really have a choice either. Shouldn't be that bad, the two possible pain points I foresee are:
The text was updated successfully, but these errors were encountered: