Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upBroken thread when a message is missing #7899
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
ariasuni
Jun 27, 2018
Contributor
If I change
to
if (status === null || status.get('content') === undefined) {then it fixes the rendering issue, although I’m not sure it’s the best way to handle that.
|
If I change to if (status === null || status.get('content') === undefined) {then it fixes the rendering issue, although I’m not sure it’s the best way to handle that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ariasuni commentedJun 27, 2018
•
edited
Edited 1 time
-
ariasuni
edited Jun 27, 2018 (most recent)
-
ariasuni
created Jun 27, 2018
Broken threads
When user3, who follows user1 but not user2, opens any toot of user1, they can see:
The JSON of
contextseems fine (contains ID of every ancestors that should be displayed) and it works in the static front-end, so retrieving the whole thread is probably an easy fix?Rendering bug
In the second case, it also triggers a nasty rendering bug:
div#mastodonto be empty.The rendering errors seem to arise from the fact that it tries to «show more» on statuses with IDs that aren’t showed in the interface.
Javascript stacktrace
master(If you're a user, don't worry about this).