#Chat Related Alerts at Top
1 messages Β· Page 1 of 1 (latest)
yep this works too. btw u missed a few syntax in the import url
dear. this doesn't work at all
okay wait
This DOES work.
I tried it with none of my CSS and it works
Okay... fixed it
For whomever this plugin doesn't work
just put it at the top priority, i.e line #1
Imports have to be at the top of a css file
Thatβs why
midnight breaks it because this uses hardcoded widths
ooh.
There are other Imports in some css snippets as well
do i copy them to the top?
Okay. Just copied... and uhm, I just found out that I was missing out on so many snippets π
Ohkay...
A bug
If I remove the uh, Import line, it returns to normal.
fixed width issues, looking into it
(line removed)
thanks π€
pushed an update, wanna check it out?
hey all! just pushed another change that allows you to update the border-radius of the alerts + an option to make them float (not be forced to the top), the variables are here
:root {
/* Set to 1 if you want them to float *\
|* Recommended while using *|
\* Midnight/Rounded Themes */
--craat-popout: 0; /* Default = 0 */
/* Change the border radius *\
\* for the alerts */
--craat-border-radius: 16px; /* default: 16px */
}
Hello! this is my first time interacting with CSS coders so don't take my words to heart π
I believe you're missing a .visual-refresh that spans around the main css code starting from .jumpToPresentBar all the way to the end of the code that prevents --craat-border-radius from being applied to both Mark as Read and Jump to Present chat alerts.
Could be a problem on my end however so I am not entirely confident in my own answer either, probably worth checking it out!
pardon me if I'm not clear enough but this is what I'm referring to visually
I am no dev, but the thingy that touches the top is fine for me, might be a theme issue idk
odd.. I'm also no theme dev but I have miniature experience from tinkering around and reading on attributes on w3schools
even with just that css-snippet applied and nothing else, it still doesn't apply the border-radius properly without adding .visual-refresh to the css
I mean, I suppose for those who do run into issues this could count as future-proofing? unsure.
and weirdly it works on the old discord ui but not on the new one for me unless I add .visual-refresh into the code
Ok after messing around for like, 1 more minute, it doesn't show any issue with yours as yours is only displaying the new messages alert.
Meanwhile the Jump to Present Alert does not get the border-radius like New Messages Alert does.
So unless New messages alert is there, Jump to Present will not be given the border-radius properly without it unless .visual-refresh {} is added to the css.
Let me quickly confirm it
okay... 2 birds in one stone ahh
You are right in your hypothesis
The Jump to present one indeed doesn't connect to the top when its alone
And the 2nd bug I found is that, the font (if that is supposed to be same) is different, and the alignment of the two icons is not the same.
I believe the 2nd bug you mentioned is from discord's end, because I had observed on the stock discord theme it was also like that, different font, font color.
and the Button mis-alignment is a sub-product of Jump to Present being placed elsewhere + differently sized so.
Makes sense
But personally for me I am unbothered by the font-difference and mis-alignment as they would most likely be a lot more code to fix them.
I've made the fix locally on my end but basically it'd look like this:
The actual code
}```
example images to show what I really mean
what is your --craat-popout set as
obviously, that's how nesting works
found out why, its a specifity issue
it's the default value
why are mine not alligned 
any other theme you are using?
Its normal behaviour
i have no idea how to properly align it because the view older messages doesnt even show how it is aligned
needs an update, I think!
any issues?
Wasn't showing up at all yesterday
wym it wasnt showing up, screenshot because it works perfectly normal for me
I mean the snippet isn't working on my machine unless I update it manually
it is at the top?
wait how did you add the snippet
quickCSS, pasted at the top of the list.
alright, imports are just stupid
just updated it for the banner for channels that arent added to your channel list
Added support for summaries
pushed some minor changes to fix the jump to present button being too big
@royal perch Hi, there does not appear to be a chatHeaderBar element any more in the CSS for this snippet to move the "You're viewing older messages" bar to the top of the window. I did make other fixes for my own copy to update all the hashes (due to the Discord CSS change), but just cannot find a way to make the bar move
i dont see any issues on mine
stable 479793 (83d195e) Host 1.0.9218 x64 (72857) Build Override: N/A Windows 11 64-bit (10.0.26200)
Vencord 6e11973 (Standalone)
Electron 37.6.0
Chromium 138.0.7204.251
Vencord 6e11973 (Standalone)
Electron 37.6.0
Chromium 138.0.7204.251```
maybe thats why, i dont use canary nowadays
ill wait for the change to be stable, but for now, i cant really fix it, i dont want to mess with canary
yeah nw, just so it helps, the bar is now here:
you could use canary web but idk how good it is lol
Adding onto the topic, it seems all the classes in canary got screwed up bad, for context this is how it looks like
Stable although looks normal, I don't know if this is/has been exclusive to canary but if this comes to stable, good lord π
it is actually intended that the hashes have changed. Discord updated rspack, which handles this hashing and it uses a new format that you can see in your screenshots: all custom CSS selectors have to be updated to support the changed format (it should be easy enough because the first 6 characters in the old selector are the same in the new one -- for the most part: the order is just different now).
it hasn't rolled out to all Stable users yet, some people have said they have it on their non-Canary desktop clients, but you will need to prepare for the change happening at some point π
Ah I see what you mean by the 6 characters not differing from the previous selectors, doesn't look that bad, assuming it doesn't change every following release
This might pose some issues with specifying things but for the most part it looks like it won't be a big deal
yeah i don't think it will change more after that, but it will need to be borne in mind. you could use wildcard selectors eg class[*="-theselectornamehere"] but you would need to take care about using them everywhere as it will have a negative impact on performance
Yeah I've meddled with those before, it'd be impractical to use wildcard selectors but if it's the only option, then hell I guess I'd be willing to tank the performance π
I might make a copy of my entire theme to work with this new system early to see if it'd work or not, so I don't have to deal with the headache later
I'd definitely recommend that you have two versions of your CSS: one for canary users and one for non-canary users. that way, if shit breaks in Canary, you can fix it for Canary and make sure it works before it goes to Stable π
An alternative is to go to different parts of the discord client, copy the html of <body> into an online html formatter and just do Ctrl+F to find the selector and copy/paste the new hash that you find, which is what i did for all my selectors in my custom CSS π€£
I'll definitely be looking into that, though I don't plan to officially maintain a Canary theme as my theme is personal use so, but it'd definitely be nice having one for cases like these I suppose
I'll also take a look into that! seems helpful!
@late parcel this is also a CSS snippet I use, perhaps you'll find a way to make this one work again and be a hero in my books for it 
I personally discovered in my own usecase that, if I for example, want to modify the userpanel area, I can do something like this:
.visual-refresh {
#app-mount [class^="_5e434"] div[class*="-sidebar"] section[class*="-panels"],
#app-mount [class^="_5e434"] section[class*="-panels"] > [class*="-container"] > [class*="-container"] {
border-radius: 0;
}
#app-mount [class^="_5e434"] div[class*="-sidebar"] section[class*="-panels"] {
left: var(--custom-guild-list-width);
bottom: 0;
width: calc(var(--custom-guild-sidebar-width) - var(--custom-guild-list-width) + 1px) !important;
background-color: color-mix(in oklab, var(--background-base-lowest), #000 11%);
}```
this works in my case, although unsure how expensive/cheap it is on performance
Unsure if this is the best place to discuss this but yeah
I cannot use something like [class$="-name"] if there's multiple classes so wildcards are the best thing I can do π , but I am VERY amateur at this so if there's a better way to do it then I have no clue
Well I guess that discussion was in vain considering discord decided to push the new classnames then revert back to the previous ones for no reason
Canary's still keeping the longer, hashed classnames though so that does make one worry
ill wait until stable
Well I guess Classname changes are back to stable, and this isn't even optimal whatsoever so I just resorted to the usual specific class targetting instead, sigh
there seems to be a margin issue between elements/segments
i dont think i accounted for summaries
and i havent used summaries for a long time
I highly recommend using https://nspc911.github.io/themes/vencord/ChatRelatedToastsAtTopv2.theme.css, but this should be updated! Any issues, please ping me, thanks!
Semi seems to overlap
(i'm using the new link you sent)
It seams to be intentional that it's transparent (unless i'm stupid)
i didnt care about the summaries
ill take a look at it if possible
its intended to be used with midnight though, forgot to mention that
Yeah I semi guessed
why are you using summaries though?
π€· It's funny sometimes and it's one of those things I turned on at one point and never turned off
I turned it off for the screenshot and I don't care enough to turn it back on
i dont have the fix at the top of my priority list
That's fine
It doesn't really matter to me
!remindme 1d perhaps fix maybe idk
Alright @royal perch, in 1 day: perhaps fix maybe idk
@royal perch, <t:1769230747:R>: perhaps fix maybe idk
!remindme 3hr
Alright @royal perch, in 3 hours: β¦
@royal perch, <t:1769318057:R>: β¦
!remindme 10mins i swear
Alright @royal perch, in 10 minutes: i swear
@royal perch, <t:1769329435:R>: i swear
@rustic oriole wait so you want me to fix for v2 or v1?
I could not really care ngl
Either
Both I guess?
damn
(if it doesn't really matter)
thanks