Local Dischorse CSS
-
-
Were @-mentions in reply chains really near-invisible until now?
-
Hmmm... they either changed the colour of @-mentions, or there was a special rule applied for chains...
Let me check on an un-updated instance.
EDIT: Damn you @riking for updating the instance!
-
I've now set them to the same colour as code blocks:
Too subtle, still?
Code, for reference:
section .embedded-posts .mention { background: rgb(224, 224, 224); }
-
looks good enough to me.
i should just turn the whole forum greyscale.
-
Styled quotes (@abarker)
aside.quote { background-color: white; border: solid 1px #0088cc; border-left-width: 5px; border-radius: 5px; } aside.quote > blockquote { background: none; border: none; } aside.quote div.title { background: none; border: none; } blockquote { background-color: white; border: solid 1px #0088cc; border-left-width: 5px; border-radius: 5px; } ```</blockquote> For those using the quote styling that included in the OP here, I made a minor correction. The styling was being hidden on markdown quotes that were in nested in BBCode quotes. To correct the issue, you can either replace the styling block wholesale, or you can just add ` > ` in the middle of `aside.quote blockquote`. That identifier was a little too broad and just needed to be limited to only target `blockquote` elements that are the immediate children of an `aside.quote` element.
-
Take your damned toasters and stuff them somewhere where the sun doesn't shine, please.
Can we add the styles for
.fa-spin
to the toasters?
-
Unfucking the latest update, I guess...
a.mention.mention { border-radius : 0; } nav.post-controls .show-replies.show-replies { font-size : 1.143em; }
(also involving a CSS hack just in case)
-
Alter font for editor text box
This specific version sets up to use monospace.Prior to Discourse 1.4.0 beta6, the composer could only be identified by its ID: wmd-input. As of Discourse 1.4.0 beta6, the composer is now assigned an ember ID (random) and wmd-input has been made a CSS class. to continue applying the correct font alterations, use the following in your local CSS:
textarea.wmd-input { font-family: monospace; }
-
Here's a handy bit of styling to make it easier to distinguish admins and mods while reading the forum:
span.username.admin * { color: #b33b00; } span.username.moderator:not(.admin) * { color: #0066cc; }
Results in this for mods:
And this for admins:
Developed by @aliceif and @yamikuronue
-
For some reason the
:not(.admin)
wasn't working for me; maybe Chrome doesn't like it. This is what I went with:span.username.admin * { color: #b33b00!important; } span.username.moderator * { color: #0066cc; }
-
My (limited) fiddling with CSS in the past suggested that the last matching directive wins. So just put the admin entry last?
-
Whoops. Somehow when I copied it, I got the
:not(.admin)
in the wrong spot. Fixed now.Though @PleegWat is correct. Putting the admin entry last will have a similar effect.
-
Test - mod-only
-
Test - admin only
-
Test - mod+admin
-
-
Interesting (not really). I hit reply and it happened to have an old saved post in here that I never finished. It also didn't give me the necrotoaster. I was confused by the old post's existence and hit cancel, closing the post. Clicked reply again and now the post is empty and the necrotoaster appears as expected.
-
A Discobug, how unexpected.