-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Chatbot component freeze when using specific LaTeX delimiters #8006
Labels
bug
Something isn't working
Priority
High priority issues
Regression
Bugs did not exist in previous versions of Gradio
Comments
BTW, gradio webUI would also break down if set
when bot returns something like \begin{equation}
E = mc^2
\end{equation} We have noticed that after adapting to gradio4. Gradio3 is fine with mathjax and mark.js |
thanks for reporting, cc @dawoodkhan82 |
2 tasks
Any updates on this?🥺 |
3 tasks
Any updates on this?🥺 |
Will take a look soon! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
Priority
High priority issues
Regression
Bugs did not exist in previous versions of Gradio
Describe the bug
The issue I'm encountering is reminiscent of the one documented in #7651. Specifically, when setting certain LaTeX delimiters (such as
\[
and\]
, or$
) within the Chatbot component, it ceases to function, accompanied by a JavaScript error identical to the one described in the referenced issue.I think this malfunction likely stems from a conflict between the JavaScript responsible for markdown rendering and that for LaTeX rendering, as both systems utilize similar notation (e.g.,
[xxx]
in Markdown). Interestingly, using$
as a LaTeX delimiter is expected to be conflict-free, I don't know what could go wrong. Besides, messages incorporating\[
and\]
consistently trigger this bug 100% of the time, whereas$
results in the bug approximately 50% of the time.Have you searched existing issues? 🔎
Reproduction
chatbots3.json
chatbots4.json
Screenshot
Logs
System Info
Severity
I can work around it
The text was updated successfully, but these errors were encountered: