98 I hate doing frontend stuff SO MUCH
Just that took me WAY too long.
I first tried bootstraps alert stuff, but that would always become too big for some idiotic reason, so after spending too much time trying to get that to work I decided to give up and use bootstraps label classes instead.
With that done it was time to put a nice icon there instead of text. Once again, no matter what I did I couldn't get it the correct height and width so it doesn't look stupid. On the rare moments that I got the correct width, half of the top if not more decided to not render. Keep in mind I didn't even try to get it at the correct place at that time so it was just awkwardly at the top right corner without any space between it and the borders which just looks plain bad.
Also, guess what? Because I couldn't get the alert class to behave I need to look into another way of making the user able to remove that warning, as the yellow is kind of distracting.
Guess its time to make a new issue in github named "replace no alert warning with icon" and label it "won't fix".
In other news, my websocket wrapper on the client now allows you to register functions for when the connection breaks. Allowing me to render those warnings when stuff breaks (which will probably happen).
The test alert now also gets properly handled on the client as it now actually looks up the username that it needs to display.
TL;DR: CSS sucks, had to work with it and nothing wanted to work. Resulted in ugly hacks and workarounds to get a less then ideal result and an angry lenscas.