Toast Content bug when using HTML strings

[David Santana Rivera]

I just noticed that in version 26.1.41 when you pass Toast Content using HTML in the string, it changes the case (from Uppercase to Lower case) of the text.

For instance, if I do this code:

private async Task showOnclick()

    {

        ToastModel toastModel = new ToastModel()

            {

               Content = "<p>Person details <b>Processed</b> successfuly!</p>",

               Title = "Success !",

               Timeout = 0

            };

            await this.toast.ShowAsync(toastModel);

    }

capital letters are changed to lower case:

You can try this same code here: https://blazorplayground.syncfusion.com/hZhfNmMMIGGdCOHl

[David Santana Rivera]

Upgraded to most recent version 26.1.42 and the issue still persists.

You can see the "bug" behavior here:

[Priyanka Karthikeyan]

Hi David Santana Rivera,

 

Thank you for your patience. We have considered the reported issue "Toast content is not displayed properly" as a bug from our end and the fix for this issue will be included in the upcoming patch release, which is scheduled for the first week of August 2024.

 

Now you can track the status of the reported issue through the feedback below,

 

Feedback link:https://www.syncfusion.com/feedback/59688/toast-content-is-not-properly-displayed

 

Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.”

 

Regards,

Priyanka K

[Priyanka Karthikeyan]

Hi David Santana Rivera,

 

We would like to inform you that we have resolved the reported issue "Toast content is not properly displayed" in our latest version 26.2.9. Therefore, we recommend that you update your package to the latest version to resolve the current problem.

 

Rootcause:

 

We identified an issue where HTML content was being incorrectly displayed in lowercase during the sanitization process. To address this, we replaced StringComparison.OrdinalIgnoreCase with StringComparison.Ordinal, which resolved the issue.

 

 

Regards,

Priyanka K