-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
markdown card. Uncaught (in promise) SyntaxError: Invalid regular expression #23050
Comments
Introduced with marked v15. |
Like mentioned above, we use marked to render markdown strings. It was recently upgraded, can you test on https://marked.js.org/demo/ ?
|
Sure thing will check. |
15.0.0 works after that no render. for now for my main laptop i could integrade more cards for my widgets in the local docker hass and dont update that. falkon is way faster browser then chrome and firefox i use normaly. |
already known in markedjs: browser is to old. |
Kde6 is not even in debian unstable. |
That specific issue doesn't seem to be the issue you see in HA, (we do polyfill for older browser), lets bump to 15.0.3 |
Tagged the bump for the 2024.12 milestone |
Checklist
Describe the issue you are experiencing
On debian stable the kde qt webengine gives a error with the markdown card. and markdown content is not shown
All QT browsers on debian (kde5) are affected. (kde6 (kde neon is not affected)
backport qt webengine also gives the error.
for example the very quick lightweight browser falkon.
Describe the behavior you expected
the markdown card to work
Steps to reproduce the issue
What version of Home Assistant Core has the issue?
2024.12.0b2
What was the last working version of Home Assistant Core?
2024.11.4
In which browser are you experiencing the issue with?
any QT web engine browser in debian bookworm
Which operating system are you using to run this browser?
debian bookworm
State of relevant entities
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
Additional information
No response
The text was updated successfully, but these errors were encountered: