How to fix display of really long comment threads?
How to fix display of really long comment threads?
Interested to see what solutions for this are proposed that don’t involve re-rooting the comment tree from a lower depth. Tesseract is susceptible to this on mobile as well, and I’ve decreased the left padding as far as it’ll go as a partial workaround.
I’m not crazy about having to re-root the comment tree like Reddit does (or at least used to do) beyond a certain depth, so hoping to hear some better suggestions I can borrow.
Haven’t used Voyager for a bit, but maybe. I’ll check and see how it does it. I’m trying to avoid that as a solution, though, if I can.
I’ve always joked (but not joking lol) that if the user has to scroll horizontally, you’ve failed as a designer. 😆
Not off my head, no. Which is why I was asking if there were any other alternatives. I don’t particularly like that solution.
Edit: Since I know the depth on a per-comment basis, maybe I could reverse it in CSS beyond a certain point and have them start going right to left? (spitballing here)
Lol, well, I’ll keep the ball rolling with this reply.
It took me a while to notice this behavior (on any client) because once a comment thread gets that deep, it’s usually a slap fight I wouldn’t bother reading anyway lol
After stopping the scroll, animate to minus padding on the left (move tree to the left in its entirety).
Or animate the margin between these comments to 0 until the end of the comments for the thread
Or just stop at some percentage of screen estate and work with differing colors.
Maybe you could use folds right above and below to indicate that the tree is rerooted?
Spittballing back. Learned a word today!
Nope. Way more hacky on the web.
On mobile it would be encapsulated and invoked on demand, easily supporting 300hz+ :).
At least I assume it; But I have my very limited experience on web development. Even if there would be an easy way due to javascript/browser compatibility it should be very cumberstone.
Though if we had a LISP-like language (Scheme) like initially intended we wouldn’t have to worry. Idk who to blame.
Someone wanted restrictions and this may have been a valid point.
I can’t judge but for mobile.
The brazen appearance of white supremacist groups in Nashville left the city grappling with how to confront hateful speech without violating First Amendment protections. They first arrived at the beginning of July: dozens of masked white supremacists, shuffling out of U-Hauls [https://x.com/kate_ross_/status/1809760867812028846], to march through Nashville carrying upside-down American flags. A week later, members of a separate neo-Nazi group, waving giant black flags with red swastikas, paraded along the city’s famed strip of honky-tonks and celebrity-owned bars. The neo-Nazis poured into the historic Metro courthouse to disrupt a City Council meeting, harassed descendants of Holocaust survivors and yelled racist slurs at young Black children performing on a downtown street. The appearance of white nationalists on the streets of a major American city laid bare the growing brazenness of the two groups, the Patriot Front and the Goyim Defense League. Their provocations enraged and alarmed civic leaders and residents in Nashville, causing the city to grapple with how to confront the groups without violating free speech protections. Non-paywall link [https://www.nytimes.com/2024/08/01/us/neo-nazis-nashville-free-speech.html?unlocked_article_code=1._00.91zO.b3mS-pBm2Sdk]
You can try adjusting the padding size; mine is on minimum and, while it still wasn’t ideal and would have gotten cut off as well if it continued, I was able to read up to the end.
Settings shortcut: Comments > Padding style
Settings shortcut: Comments > Padding style
Setting this to minimum helped me