site banner

Small-Scale Question Sunday for September 04, 2022

Do you have a dumb question that you're kind of embarrassed to ask in the main thread? Is there something you're just not sure about?

This is your opportunity to ask questions. No question too simple or too silly.

Culture war topics are accepted, and proposals for a better intro post are appreciated.

26
Jump in the discussion.

No email address required.

Roll call! Who made it over?

I'm here.

Shambled to see that the comments are still floating in a sea of whitespace. I'd try to come up with some fixed CSS myself, but the idea that I'm supposed to make a PR on Github (and hence either associate my name-linked Github account or jump through whatever hoops are necessary to make a new and unassociated one) is discouraging.

edit: I'm using the following custom CSS now to have a bit more sanity:


*:not(.comment-text p) {

margin: 0px !important;

}


.comment-text p+p {

margin-top: 1rem !important;

margin-bottom: 0px !important;

margin-left: 0px !important;

margin-right: 0px !important;

}


.comment-text p:not(p+p) {

margin: 0px !important;

}


.comment, .comment-text {

padding-top: 0px !important;

padding-bottom: 0px !important;

}


.comment-collapse-desktop {

padding-right: 15px !important;

}


.list-inline-item {

margin-right: 5px !important;

}


.profile-pic-25 {

scale: 0.5 !important;

}

Unfortunately, main.css has a few !importants of its own enforcing padding (in particular on .comment .comment-body .comment-text) which I can't override.

edit2: The markdown parser doubles newlines in the three-backtick code span.

you can override main.css's !importants by giving your rules higher css precedences and also !important iirc. you can beat .comment .comment-body .comment-text with something like .. comment .comment-body .comment-text

edit2: The markdown parser doubles newlines in the three-backtick code span.

Also lists are possibly broken (plus there's too much spacing between items)

  • test

  • second

    • second level

    • sth sth

Known bug; we've actually had a half-finished fix for a while, but the person who wrote it hasn't had time to finish it, and we've been working on other stuff.

I definitely plan to go over the comment theme and make a bunch of changes. It wasn't the priority - the main page was worse - and then I ended up not getting to it before the launch.