You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some incoming links to threads with forks stop all forks in that thread from rendering.
Post A links to topic B, and topic B is the root of a fork-chain. Post A does not fork, and just links to topic B.
If the link to topic B from post A is a link to the root URL of the topic (https://bbu.world/t/collaborative-whaling/1039), then none of the forks render when topic B is shown in the reader.
I suspect that this is a problem because post A contains videos, so that when the reader looks at the HTML for post A when loading topic B, it crashes before it gets to rendering the forks.
As there is a hack around this it's possible to use the reader with this error, but as it produces some pretty confusing behavior, it should be fixed eventually.
The text was updated successfully, but these errors were encountered:
Some incoming links to threads with forks stop all forks in that thread from rendering.
Post A links to topic B, and topic B is the root of a fork-chain. Post A does not fork, and just links to topic B.
If the link to topic B from post A is a link to the root URL of the topic (https://bbu.world/t/collaborative-whaling/1039), then none of the forks render when topic B is shown in the reader.
If the link to post B from post A is a link to the fourth post in the topic (https://bbu.world/t/collaborative-whaling/1039) then the last fork is not loaded while the others are.
I suspect that this is a problem because post A contains videos, so that when the reader looks at the HTML for post A when loading topic B, it crashes before it gets to rendering the forks.
It's possible to hack this problem by linking post A to a non-existant post in topic B, for example (https://bbu.world/t/collaborative-whaling/1039/10) as topic B only has 4 replies.
As there is a hack around this it's possible to use the reader with this error, but as it produces some pretty confusing behavior, it should be fixed eventually.
The text was updated successfully, but these errors were encountered: