Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Mon, Nov 6, 2023 10:06 PM UTC in reply to H. G. Muller from Fri Nov 3 08:20 AM:

The announcement on some pages (including the Featured Variants page) uses black font in the black box, which doesn't make it very readable.

This is a problem with pages that use /g/globalindex.css instead of /g/global.css. In examining the two files, the relevant CSS seems to be the same. And when using Web Developer Tools in Firefox to examine the actual CSS in use, the page with /g/globalindex.css says the color is rgb(0, 0, 0), and the one that works right says the color is rgb(245, 245, 220). When I double-click on each color value, I get the same results with just a difference in file name and line numbers. Each says that the best match is beige for .blackbox, and the parent match is plum for .notice. When I added an !important to the plum color in notice, it said the best match was plum in .notice, but it still displayed the text as black. So, I don't know why it is displaying the text as black. While switching pages to /g/global.css would fix the problem on a page-by-page level, I would like to fix it in the CSS file, which I don't know how to do short of making both files identical.


Edit Form

Comment on the page Featured Chess Variants

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.