From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Cc: Jason Merrill <jason@redhat.com>
Subject: [wwwdocs] [1/3] projects/cxx-status.html -- introduce global CSS for tables
Date: Sat, 02 Apr 2016 10:20:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1604021441201.9804@anthias.pfeifer.com> (raw)
Jason pointed out that https://gcc.gnu.org/projects/cxx-status.html
looks as if it ignored all the CSS on that page, whereas things look
fine on his local system.
This is another victim of the strict Content Security Policy someone
put in place earlier this year, and luckily one of the last instances.
Which I am going to take care of now. ;-)
Below the first patch, after which things start looking at least
remotely sensible again.
(Note that we do not need this for the table itself; doing this
for its cells is sufficient.)
Committed.
Gerald
ChangeLog:
Introduce a new CSS class table.cxxstatus that draws a grid around
table cells. Use that class throughout projects/cxx-status.html
and add a missing empty cell (<td></td>). Remove local CSS that
accomplished the same.
Index: gcc.css
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc.css,v
retrieving revision 1.33
diff -u -r1.33 gcc.css
--- gcc.css 7 Feb 2016 15:05:47 -0000 1.33
+++ gcc.css 2 Apr 2016 09:33:10 -0000
@@ -64,6 +64,9 @@
/* Quote an e-mail. The first <div> has the sender, the second the quote. */
blockquote.mail div:nth-child(2) { border-left: solid blue; padding-left: 4pt; }
+/* C++ status tables. */
+table.cxxstatus th, td { border: 1px solid gray; }
+
/* Classpath versus libgcj merge status page. */
.classpath-only { background-color: #FFFFAA; }
Index: projects/cxx-status.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/cxx-status.html,v
retrieving revision 1.2
diff -u -r1.2 cxx-status.html
--- projects/cxx-status.html 16 Mar 2016 03:20:58 -0000 1.2
+++ projects/cxx-status.html 2 Apr 2016 09:33:11 -0000
@@ -6,7 +6,6 @@
tr.separator { background: #ffffcc}
.supported { color: green }
.unsupported { color: red }
- table, td, th { border: 1px solid gray }
/* ]]> */
</style>
</head>
@@ -57,7 +56,7 @@
version of GCC that contains an implementation of this feature (if
it has been implemented).</p>
- <table>
+ <table class="cxxstatus">
<tr class="separator">
<th>Language Feature</th>
<th>Proposal</th>
@@ -192,7 +191,7 @@
<td> </td>
</tr>
-->
- <table>
+ <table class="cxxstatus">
<tr class="separator">
<th>Technical Specification</th>
<th>Document</th>
@@ -233,7 +232,7 @@
feature, while the "Available in GCC?" column indicates the first
version of GCC that contains an implementation of this feature.</p>
- <table>
+ <table class="cxxstatus">
<tr class="separator">
<th>Language Feature</th>
<th>Proposal</th>
@@ -341,7 +340,7 @@
part of the published standard; as a result, it has been removed from
the compiler.</p>
- <table>
+ <table class="cxxstatus">
<tr class="separator">
<th>Language Feature</th>
<th>Proposal</th>
@@ -378,7 +377,7 @@
<li><a href="../gcc-4.8/cxx0x_status.html">GCC 4.8 C++11 Status</a></li>
</ul>
- <table>
+ <table class="cxxstatus">
<tr class="separator">
<th>Language Feature</th>
<th>Proposal</th>
@@ -390,6 +389,7 @@
<td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2118.html">N2118</a></td>
<td style="text-align:center;"><a href="../gcc-4.3/changes.html">GCC 4.3</a></td>
<td>__cpp_rvalue_references >= 200610</td>
+ <td></td>
</tr>
<tr>
<td> Rvalue references for <code>*this</code></td>
next reply other threads:[~2016-04-02 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 10:20 Gerald Pfeifer [this message]
2016-04-02 13:40 ` [wwwdocs] [2/3] " Gerald Pfeifer
2016-04-02 13:46 ` [wwwdocs] [3/3] " Gerald Pfeifer
2016-04-04 10:19 ` [wwwdocs] [4/3] " Gerald Pfeifer
2016-04-05 13:14 ` [wwwdocs] [1/3] " Jason Merrill
2016-04-05 15:43 ` Gerald Pfeifer
2016-04-05 16:04 ` [wwwdocs] [5/3] " Gerald Pfeifer
2016-04-05 16:23 ` [wwwdocs] [1/3] " Gerald Pfeifer
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=alpine.LSU.2.20.1604021441201.9804@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).