public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH htdocs] schedule: move css to sep file
Date: Sat, 30 Dec 2023 12:51:27 -0500	[thread overview]
Message-ID: <20231230175127.2037-1-vapier@gentoo.org> (raw)

The sourceware.org site is using CSP which blocks inline <style> tags.
Move it to a sep file so it loads & renders correctly.
---
 css/schedule.css    | 42 ++++++++++++++++++++++++++++++++++++++++++
 schedule/index.html | 43 ++-----------------------------------------
 2 files changed, 44 insertions(+), 41 deletions(-)
 create mode 100644 css/schedule.css

diff --git a/css/schedule.css b/css/schedule.css
new file mode 100644
index 000000000000..a5cc139bbe7e
--- /dev/null
+++ b/css/schedule.css
@@ -0,0 +1,42 @@
+@charset "utf-8";
+
+/**
+ * History columns (i.e. nth-child):
+ * 1 - Release
+ * 2 - Estimate
+ * 3 - Schedule
+ * 4 - Actual
+ * 5 - slip
+ * 6 - comment
+ */
+
+table#history {
+  /* Align the table in the center. */
+  margin-left: auto;
+  margin-right: auto;
+}
+
+table#history th {
+  padding-right: 0.5em;
+  vertical-align: middle;
+}
+
+/* For long comments that wrap, make sure the other columns are at the top.  */
+table#history tr {
+  vertical-align: top;
+}
+
+table#history td {
+  /* Make sure dates don't run together.  */
+  padding-right: 0.5em;
+  white-space: nowrap;
+}
+
+table#history tr > td:nth-child(5) {
+  text-align: center;
+}
+
+table#history tr > td:nth-child(6) {
+  text-align: left;
+  white-space: normal;
+}
diff --git a/schedule/index.html b/schedule/index.html
index 1c7f92bc2a2e..beb32cfa43e1 100644
--- a/schedule/index.html
+++ b/schedule/index.html
@@ -78,50 +78,11 @@ equivalent amount.
 
 <center><h3>Schedule History (approximate)</h3></center>
 
-<style>
-/**
- * History columns (i.e. nth-child):
- * 1 - Release
- * 2 - Estimate
- * 3 - Schedule
- * 4 - Actual
- * 5 - slip
- * 6 - comment
- */
-
-table#history {
-  /* Align the table in the center. */
-  margin-left: auto;
-  margin-right: auto;
-}
-
-table#history th {
-  padding-right: 0.5em;
-}
-
-/* For long comments that wrap, make sure the other columns are at the top.  */
-table#history tr {
-  vertical-align: top;
-}
-
-table#history td {
-  /* Make sure dates don't run together.  */
-  padding-right: 0.5em;
-  white-space: nowrap;
-}
-
-table#history tr > td:nth-child(5) {
-  text-align: center;
-}
-
-table#history tr > td:nth-child(6) {
-  text-align: left;
-  white-space: normal;
-}
-</style>
+<link rel="stylesheet" href="../css/schedule.css" />
 
 <table id=history>
 
+<!-- Keep columns in sync with the CSS -->
 <tr> <th>Release</th><th>Estimate</th><th>Schedule</th><th>Actual</th><th>Slip (months)</th><th align=left>Comment</th></tr>
 
 <tr>
-- 
2.43.0


                 reply	other threads:[~2023-12-30 17:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231230175127.2037-1-vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).