Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

639

Hey poalacks,

I'd like you to take notice, that there are some people, who are enjoying longer discussions, which are discouraged by your current CSS.

As an example, you could look at the following thread, where some user tries to (unsuccessfully) argue for being thoughtful towards boomers:

https://poal.co/s/Helicoptarian/133661

The fact, that every few messages require a reload sucks just as much as the fact, that the discussion becomes unreadable after a while, because the <div> becomes too narrow to even display single words in one line.

Hey poalacks, I'd like you to take notice, that there are some people, who are enjoying longer discussions, which are discouraged by your current CSS. As an example, you could look at the following thread, where some user tries to (unsuccessfully) argue for being thoughtful towards boomers: https://poal.co/s/Helicoptarian/133661 The fact, that every few messages require a reload sucks just as much as the fact, that the discussion becomes unreadable after a while, because the <div> becomes too narrow to even display single words in one line.

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (17).
[–] • 1 pt

Yes, currently the only way to follow a deep thread is to continue clicking permalinks to the comments in order to reset the margin width.

They've known about it for a while. But what is the solution?

[–] • 2 pts

I
'
v
e

g
o
t

i
t
.

J
u
s
t

v
e
r
t
i
c
a
l
l
y

a
r
r
a
n
g
e

c
o
m
m
e
n
t
s

f
r
o
m

t
h
e

s
t
a
r
t

t
o

s
a
v
e

r
o
o
m
!

[–] • 1 pt

I found the solution! See above.

[–] • 1 pt

PERFECT! Will implement immediately.

[–] • 0 pt

The margin to the left of the message-divs is too large. Should be like the margin on the right, which is smaller. It also may be possible to use different CSS classes, depending on how big a thread is.

It should also be possible to open a whole tree, or at least a complete branch of the tree, with one click, or at least until another fork happens. Clicking for every few instances down the tree kinda sucks. With tree I mean the structure under which the messages are organized.

This shouldn't cause too much trouble with the database, if the relevant fields are indexed, and the objects are retrieved in one single operation.

[–] • 0 pt

You could probably fix this with a custom sub CSS, which you (or any other user) could then apply globally in your settings. If you give it a try please let me know.

[–] • 1 pt (edited )

I've made a few changes to the CSS, so that less space is wasted:

https://poal.co/s/WMDTestSite/135282

Put the following into your CSS, if you want to use this design:

/* CSS here */

.pchild {
  margin-left: 0px;
}

.c-upvote, .c-downvote, .upvote, .downvote {
  width: 12px;
}

.votecomment {
  width: 16px;
}

.commentrow.text-post.no-padding.comment {
  padding: 0.4em 0 0.4em 0.4em;
}

article.comment:nth-child(n) {
  -webkit-box-shadow: none;
  -moz-box-shadow: none;
  box-shadow: none;
  border: 2px solid #333;
  border-right: none;
}

article.comment:first-of-type {
  border-radius: 8px;
}
[–] • 1 pt

How/where can I customize the CSS?