this post was submitted on 05 Aug 2024
60 points (98.4% liked)
Sync for Lemmy
15088 readers
1 users here now
๐
Welcome to Sync for Lemmy!
Welcome to the official Sync for Lemmy community.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Community Rules
1- No advertising or spam.
All types of advertising and spam are restricted in this community.
Community Credits
Artwork and community banner by: @[email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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)
We should start a ridiculously long comment thread here so people can see how the various Lemmy apps out there handle and render things...
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
i'm tempted to make a stupid feature where it turns into an ace attorney fight after about 15 comments of depth.
Pee is stored in the balls. Wanna fight about it?
How could I fight with the truth? Gonna need a different argument.
@[email protected]
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!
Yeah thatd work, but it would probably be pretty hard to do on mobile
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.