1 files changed, 25 insertions, 29 deletions

diff --git a/static/style.css b/static/style.css
index 8f3d72d..bf1e07f 100644
--- a/static/style.css
+++ b/static/style.css
@@ -58,7 +58,6 @@
 html {
 	font-family: system-ui, sans-serif;
 	line-height: 1.2;
-	border-color: var(--theme); /* FIXME: what is this */
 	background-color: var(--primary-bg);
 	color: var(--primary-fg);
 }
@@ -79,15 +78,6 @@ footer {
 }
 
 /*
- * Should probably not use <hr />'s in normal use...
- */
-hr {
-	background-color: black;
-	border-width: 0;
-	height: 1px;
-}
-
-/*
  * For accessibility reasons, we still want anchors to be underlined, but
  * perhaps not as profound of an underline as the default.
  */
@@ -311,6 +301,18 @@ a.btn {
 	border: none;
 }
 
+.message-box {
+	margin: auto;
+	max-width: 30rem;
+	border: solid 2px var(--border);
+	background-color: var(--box);
+	padding: 0rem 1rem;
+}
+
+table#table-of-courses {
+	width: 100%;
+}
+
 /*
  * .need-connection is the content that should actually display when we are
  * connected via WebSocket. The JavaScript would change display from none to
@@ -319,35 +321,29 @@ a.btn {
 .need-connection {
 	display: none;
 }
+
 /*
- * .before-connection displays the pre-connection message, and the JavaScript
- * does the exact opposite.
+ * Same for script-required, though the JavaScript hides this as soon as it's
+ * loaded.
  */
-.before-connection {
+.script-required {
+	display: none;
 }
+
 /*
  * .broken-connection displays a message telling users to refresh the page,
- * after their WebSocket connection breaks.
+ * after their WebSocket connection breaks. It should be hidden by default.
  */
 .broken-connection {
 	display: none;
 }
-.script-required {
-	display: none;
-}
-
-.message-box {
-	margin: auto;
-	max-width: 30rem;
-	border: solid 2px var(--border);
-	background-color: var(--box);
-	padding: 0rem 1rem;
-}
-
-table#table-of-courses {
-	width: 100%;
-}
 
+/*
+ * This site heavily uses CSS styling to display and hide messages, so by
+ * default we put a big warning about CSS being broken, which disappears
+ * once the main CSS, i.e. this file, is completely loaded. Therefore it's
+ * probably best to put this at the bottom of this file.
+ */
 .broken-styling-warning {
 	display: none;
 }