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.
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
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.
How about this: as you scroll past an entire comment in the chain (the bottom of the comment leaves the top of the screen) the entire comment chain is shifted to the left?