-
Notifications
You must be signed in to change notification settings - Fork 150
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
Option not to escape HTML in message #226
Comments
Have you tried the component prop:
|
Hi @Vadorequest, there is no maybe something like this.
|
Thank you both, I used the toastr.error(title, {
position: 'bottom-left', // Because in production, in the iframe, we don't see them if they're on top
timeOut: fields.length * 4000, // Display the message 4s per error, so that the user has time to see all missing fields (UX)
component: <p dangerouslySetInnerHTML={{ __html: message }} />,
closeOnToastrClick: false,
}); |
It does generate a react warning though:
|
Is HTML escaped in the message by default?
I'm doing the following
which displays this:
Am I doing something wrong? I'd assume using HTML within the message would be tolerated, maybe through a flag if not enabled by default for security reasons.
The text was updated successfully, but these errors were encountered: