[bug] Escaped HTML post rendering problem #847
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#847
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
From source
Extra details
No response
Version
v3.13.2 with https://akkoma.dev/AkkomaGang/akkoma-fe/commit/4a50b12
PostgreSQL version
14
What were you trying to do?
No response
What did you expect to happen?
No response
What actually happened?
The user on my instance reported me a bug where the timeline and notifications stopped rendering for them.
As they told, this happened after they made a particular post with HTML type. After opening the post by its URL, it doesn't render for me either.
I got original post content, before it was HTML processed, and tried to look it up through Preview on Akkoma-FE and had the same rendering problem.
The post content:
If I manually strip all escape symbols, the post gets rendered normally:
Another broken case:
This might be an Akkoma-FE bug, but I'm unsure.
Logs
No response
Severity
I cannot use the software
Have you searched for this issue?
Yet another broken case:
Broken:
<a href=\"https://akkoma.dev/AkkomaGang/akkoma/issues/847\">issue</a>
Works:
<a href="https://akkoma.dev/AkkomaGang/akkoma/issues/847">issue</a>
This is especially dangerous as it affects both HTML and Markdown post type.
Does the API query error out and if so with what response?
Do server-side logs show anything related?
@Oneric no, nothing times out.
Result reply from the API is in the attachments. I didn't notice that before but it gets rendered fine on Husky but completely breaks the FE.