Closed eatyourgreens closed 3 months ago
Turns out this is a side effect of a bigger bug, which is that Talk search results are being displayed as raw markdown strings. The HTML parser in the Markdown
component errors if it's passed a string that can't be parsed as HTML.
Expected behavior
Talk should try to display comments, even with invalid characters?
Current behavior
A blank white page, with the error thrown in the dev console.
Steps to replicate
https://www.zooniverse.org/talk/search?page=11&query=add
Additional context
There's some text in a comment which Markdown is attempting to parse as a React component.