Change History
New api methods will be announced here. Changes in our data that is relevant to checkers scripts/tags will also be announced here.
Changed By: KaiserVonChina
Change Date: February 14, 2026 11:19PM
Re: Checker CSS and helper functions
Thanks for the changes you plan to do.
Here is how my table looks like with your class "table-bordered":
[img]https://s3.amazonaws.com/gs-geo-images/2db127ae-57da-4228-92f2-5c215f1139dd.png[/img]
Notice that everything is left-aligned and how badly the border is visible between the cache types.
Here is how I would like it to look like:
[img]https://s3.amazonaws.com/gs-geo-images/a9bd6220-67c6-477b-a353-601222e7bf08.png[/img]
A "one size fits all" design is a nice idea, but it will never fit all requirements of real life. Sure you can't provide classes for every possible variant, but having more than one option to choose from would be nice.
Here is another example where I use 2 different color sets for a striped table:
[img]https://s3.amazonaws.com/gs-geo-images/5c9eb76f-1de4-44b9-932e-b25442f0d6c2.png[/img]
I'm pretty sure that the background colors can't be fit into a CSS class, since I'm using "rowspan" with different numbers of rows here and those numbers are not fixed but depend on values from the tag configuration. But again I can't imagine which sets of background colors would fit nicely to your light-gray border color in such a table.
P.S.: If you would like a more uniform design, you can define background colors for table cells that are
- not fulfilled (usually red is used in checkers so far)
- partially fulfilled (usually some kind of yellow or orange))
- fulfilled (some kind of green)
- fulfilled and selected (some other kind of green)
Example: Find some number of unique pairs of A and B with at least C caches that have both properties A and B.
Table cells with less than C caches would be "partially fulfilled", table cells with at least C caches would be "fulfilled". Table cells with at least C caches that are selected as unique pairs would be "fulfilled and selected".
Table cells that are not considered or empty usually keep their default (white) background.
Original Message
Author: KaiserVonChina
Date: February 14, 2026 10:24PM
Re: Checker CSS and helper functions
Thanks for the changes you plan to do.
Here is how my table looks like with your class "table-bordered":
[img]https://s3.amazonaws.com/gs-geo-images/2db127ae-57da-4228-92f2-5c215f1139dd.png[/img]
Notice that everything is left-aligned and how badly the border is visible between the cache types.
Here is how I would like it to look like:
[img]https://s3.amazonaws.com/gs-geo-images/a9bd6220-67c6-477b-a353-601222e7bf08.png[/img]
A "one size fits all" design is a nice idea, but it will never fit all requirements of real life. Sure you can't provide classes for every possible variant, but having more than one option to choose from would be nice.
Here is another example where I use 2 different color sets for a striped table:
[img]https://s3.amazonaws.com/gs-geo-images/5c9eb76f-1de4-44b9-932e-b25442f0d6c2.png[/img]
I'm pretty sure that the background colors can't be fit into a CSS class, since I'm using "rowspan" with different numbers of rows here and those numbers are not fixed but depend on values from the tag configuration. But again I can't imagine which sets of background colors would fit nicely to your light-gray border color in such a table.