This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Has anyone tried to get the classes and colors into MediaWiki:Common.css? The table-
prefix is actually unnecessary if you use selectors like th.yes, td.yes
. One could still overwrite them in a user stylesheet. — Christoph Päper 17:32, 9 September 2009 (UTC)
Template | Class | Default text | Background | Color | Other styles |
---|---|---|---|---|---|
((rh)) | rh | #ECECEC | black | text-align: left; padding-left: 0.5em; font-weight: bold; | |
((rh2)) | rh | #EEDDFF | black | text-align: left; padding-left: 0.5em; font-weight: bold; | |
((yes)) | yes | Yes | #90FF90 | black | |
((no)) | no | No | #FF9090 | black | style parameter |
((BLACK)) | no | N/A | #000000 | ||
((siteactive)) | siteactive | Active | #90FF90 | black | |
((siteinactive)) | siteinactive | Inactive | #FF9090 | black | style parameter |
((yes2)) | yes2 | #DDFFDD | black | ||
((no2)) | no2 | #FFDDDD | black | ||
((won)) | yes2 | Won | #CCFFCC | black | text-align: align parameter; vertical-align: middle; |
((nom)) | no2 | Nominated | #FFFFDD | black | text-align: align parameter; vertical-align: middle; |
((partial)) | partial | Partial | #FFFFDD | black | |
((Yes-No)) | partial | Yes/No | #FFFFDD | black | |
((some)) | partial | Some | #FFFFDD | black | |
((any)) | any | any | #FFFFDD | black | |
((n/a)) | na | N/A | #ECECEC | grey | |
((dunno)) | unknown | ? | #FFFFFF | black | |
((unk)) | unknown | Unknown | #E4E4E4 | black | |
((depends)) | depends | Depends | #FFEEDD | black | |
((included)) | included | Included | #DDFBFF | black | |
((dropped)) | dropped | Dropped | #FFEEDD | black | |
((terminated)) | dropped | Terminated | #EEDDFF | black | |
((beta)) | beta | Beta | #DFDFFF | black | |
((table-experimental)) | beta | Experimental | #DFDFFF | black | |
((free)) | free | Free | #99FFFF | black | |
((nonfree)) | nonfree | #FF99DD | black | ||
((needs)) | needs | Needs | #FF9090 | black | |
((incorrect)) | incorrect | Incorrect | #FF9900 | black | |
((no result)) | no result | No result | #DFDFFF | black | text-align: align parameter; vertical-align: middle; |
((pending)) | pending | Pending | #FFFFDD | black |
Code | Red | Green | Blue | Hue | Saturation | Lightness | Suggestion |
---|---|---|---|---|---|---|---|
000000 |
0 | 0 | 0 | 0° | 0% | 0% | 000
|
90FF90 |
144 | 255 | 144 | 120° | 100% | 75% | 9F9
|
99FFFF |
153 | 255 | 255 | 180° | 100% | 80% | 9FF
|
CCFFCC |
204 | 255 | 204 | 120° | 100% | 90% | CFC
|
DDFBFF |
221 | 251 | 255 | 187° | 100% | 93% | DFF
|
DDFFDD |
221 | 255 | 221 | 120° | 100% | 93% | CFC
|
DFDFFF |
223 | 223 | 255 | 240° | 100% | 94% | DDF
|
E4E4E4 |
228 | 228 | 228 | 0° | 0% | 89% | EEE
|
ECECEC |
236 | 236 | 236 | 0° | 0% | 93% | EEE
|
EEDDFF |
238 | 221 | 255 | 270° | 100% | 93% | DDF
|
FF9090 |
255 | 144 | 144 | 0° | 100% | 78% | F99
|
FF9900 |
255 | 153 | 0 | 36° | 100% | 50% | F90
|
FF99DD |
255 | 153 | 221 | 320° | 100% | 80% | F9D
|
FFDDDD |
255 | 221 | 221 | 0° | 100% | 93% | FDD
|
FFEEDD |
255 | 238 | 221 | 30° | 100% | 93% | FDD
|
FFFFDD |
255 | 255 | 221 | 60° | 100% | 93% | FFD
|
FFFFFF |
255 | 255 | 255 | 0° | 0% | 100% | FFF
|
The colors #CCFFCC
and #DDFFDD
, #ECECEC
and #E4E4E4
are basically indistinguishable, #DFDFFF
and #EEDDFF
are also too close. We should either use digit doubles (like #FFCC99
) or zero-padding (like FFC090
), CSS uses the former for three-hexdigit colors (like #FC9
) – as long as we don’t use optimized colors without looking at the hexadecimal RGB codes.
Except for rh
all templates should probably be of this form:
style="background: #ABCDEF; color: black; text-align: (({align|center))}; (({style|))}" class="Class without table-"|(({1|Default text))}
With inclusion into MediaWiki:Common.css this would become:
style="text-align: (({align|center))}; (({style|))}" class="Class without “table-”"|(({1|Default text))}
or
style="(({style|))}" class="Class without “table-”"|(({1|Default text))}
or just
class="Class without “table-”"|(({1|Default text))}
.There are many flags that could be used in WP tables, here are some I could think of.
I believe a scale of five background colors (including the three known from traffic lights) together with one for the indeterminate state (probably gray) should cover most cases. We might want to provide two sets of these, one vivid, one pale. — Christoph Päper 14:39, 10 September 2009 (UTC) PS: When some of these were using icons instead of text it was much more feasible to use templates rather than just classes.
Pale color | green | blue | yellow | orange | red | gray |
---|---|---|---|---|---|---|
Vivid color | green | blue | yellow | orange | red | gray |
Standard color | green | blue | yellow | orange | red | gray |
((Match)) | ((win)) | no result=((future)) | ((play)), ((in play)) | ((tie)), ((remis)), ((draw)) | ((lose)) | no result=((unknown)) |
((Competition)) | ((won)), ((first)), ((best)), ((gold)) | ((place)), ((runner-off)), ((silver)) + ((bronze)), ((second)) + ((third)) | ((qualified)), ((QF)) | ((disqualified)), ((DQ)) | ((not qualified)), ((NQ)) | |
((Award)) | ((won)) | ((nominated)), ((nom)) | ((not nominated)) | |||
((Ranking)), ((rank)) | ((best)) | ((good)) | ((average)), ((avg)) | ((bad)) | ((worst)) | |
((Truth)) | ((yes)), ((true)) | ((maybe)), ((unknown)), ((unk)), ((uncertain)) | ((yes-no)), ((but)) | ((no)), ((false)) | ((not available)), ((NA)), ((N/A)) | |
((Validity)), ((valid)) | ((correct)), ((right)) | ((indeterminate)) | ((incorrect)) | ((wrong)) | ((no result)), ((pending)) | |
((Activity)) | ((active)) | ((interactive)) | ((paused)) | ((inactive)) | ((passive)) | |
((Scale)) | ((max)), ((maximum)) | ((med)), ((medium)), ((middle)), ((mid)), ((median)) | ((avg)), ((average)), ((mean)) | ((min)), ((minimum)) | ||
((Measure)), ((size)) | ((huge)), ((XL)) | ((large)), ((L)) | ((medium)), ((M)) | ((small)), ((S)) | ((smallest)), ((XS)) | |
((Value)) | ((highest)) | ((high)) | ((normal)) | ((low)) | ((lowest)) | |
((Quantity)) | ((all)), ((every)) | ((many)), ((most)), ((much)) | ((some)) | ((few)), ((any)) | ((none)), ((nil)) | |
((Quality)) | ((best)) | ((good)) | ((neutral)) | ((bad)) | ((worst)), ((evil)) | |
((Frequency)), ((freq)) | ((always)) | ((often)), ((usual)) | ((sometimes)) | ((rare)), ((seldom)) | ((never)) | |
((Temperature)), ((temp)) | ((moderate)) | ((cold)), ((freezing)) | ((warm)) | ((hot)), ((boiling)), ((burning)) | ||
((Product)) ((phase)), ((cycle)) | ((current)), ((in production)), ((production)) | ((Beta)), ((in development)), ((development)), ((pending)); ((RC)), ((release candidate)), ((in testing)), ((testing)), ((test)) | (((proposal)) but) ((rejected)), ((deprecated)) | ((outdated)), ((abolished)) | ((antique)), ((dropped)), ((terminated)) | ((Alpha)), ((planned)), ((proposed)), ((announced)), ((nightly)),((experimental)), ((in research)), ((research)) |
((Feature)) ((implementation)) | ((has)) (((present))) | ((will have)) (((future))) | ((may have)) (present) | ((had)) (((past))) | ((has not)) (present) | |
((Feature)) ((support)) | ((full)), ((complete)), ((default)), ((included)) | ((extended)), ((optional)) | ((basic)), ((version)) | ((some)), ((partial)), ((incomplete)), ((limited)), ((depends)), ((buggy)), ((excluded)) | ((none)) | |
((Price)) | ((share)), ((donate)), ((cheap)) | ((free)) | ((rent)), ((lease)), ((subscribe)) | ((pay)), ((buy)), ((retail)) | ((expensive)) | ((not for sale)), ((unique)) |
((Source)) ((code)), ((license)) | ((open)) | ((shared)) | ((licensed)) | ((closed)) | ||
((Gender)), ((sex)) | ((neuter)) | ((male)) | ((female)) | |||
((Sexuality)) | ((heterosexual)) | ((bisexual)) | ((homosexual)), ((gay)), ((lesbian)) | ((asexual)) | ||
Pale color | green | blue | yellow | orange | red | gray |
Vivid color | green | blue | yellow | orange | red | gray |
Standard color | green | blue | yellow | orange | red | gray |
Name | Code | Red | Green | Blue | Hue | Sat. | Light. | Code | Red | Green | Blue | Hue | Sat. | Light. | Code | Red | Green | Blue | Hue | Sat. | Light. |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
green | EEFFDD |
238 | 255 | 221 | 90° | 100% | 93% | CCFF99 |
204 | 255 | 153 | 90° | 100% | 80% | 80FF00 |
128 | 255 | 0 | 90° | 100% | 50% |
lime | DDFFDD |
221 | 255 | 221 | 120° | 100% | 93% | 99FF99 |
153 | 255 | 153 | 120° | 100% | 80% | 00FF00 |
0 | 255 | 0 | 120° | 100% | 50% |
green | DDFFEE |
221 | 255 | 238 | 150° | 100% | 93% | 99FFCC |
153 | 255 | 204 | 150° | 100% | 80% | 00FF80 |
0 | 255 | 128 | 150° | 100% | 50% |
blue/cyan | DDFFFF |
219 | 255 | 255 | 180° | 100% | 93% | 99FFFF |
153 | 255 | 255 | 180° | 100% | 80% | 00FFFF |
0 | 255 | 255 | 180° | 100% | 50% |
yellow | FFFFDD |
255 | 255 | 221 | 60° | 100% | 93% | FFFF99 |
255 | 255 | 153 | 60° | 100% | 80% | FFFF00 |
255 | 255 | 0 | 60° | 100% | 50% |
orange | FFEEDD |
255 | 238 | 221 | 30° | 100% | 93% | FFCC99 |
255 | 204 | 153 | 30° | 100% | 80% | FF8000 |
255 | 128 | 0 | 30° | 100% | 50% |
red | FFDDDD |
255 | 221 | 221 | 0° | 100% | 93% | FF9999 |
255 | 153 | 153 | 0° | 100% | 80% | FF0000 |
255 | 0 | 0 | 0° | 100% | 50% |
gray | EEEEEE |
238 | 238 | 238 | 0° | 0% | 93% | CCCCCC |
204 | 204 | 204 | 0° | 0% | 80% | 808080 |
128 | 128 | 128 | 0° | 0% | 50% |
Pale | Vivid | Standard |
Many of the (good) template names are taken. We could introduce a special character, a kind of a poor man’s namespace, for example ((!foo|bar)), ((foo!|bar}, ((foo-|bar)), ((-foo|bar)), ((Tfoo|bar)), ((table-foo|bar)), ((cell-foo|bar)), ((cell|foo|bar))
. I like the appended exclamation mark. — Christoph Päper 14:41, 16 March 2010 (UTC)
When did the color change from green to blue? That affects every single article and infobox providing a summary for the awards and nominations received by musicians, etc. Was there a discussion relating to this color change? --Another Believer (Talk) 06:23, 17 February 2010 (UTC)
((editsemiprotected)) Undo last edit to fix chinese character
213.106.225.195 (talk) 13:02, 26 March 2010 (UTC)
The shade of green currently in use is quite difficult to differentiate from the shade of red (Template:Won vs.Template:Nom). I am red-green colour-blind to an extent and believe me it is difficult to differentiate!--JovianEye (talk) 19:16, 25 April 2010 (UTC)
Former | Former |
Former | Temporary |
Current | Current |
Proposed | Proposed |
((Yes)) | ((No)) |
May 13 | May 13 |
I've added the colours from some former versions and from the ((Yes)) and ((No)) templates for comparison. My impression is that the proposed green is too similar to the green from the Yes template. The (current) blue tint was used supposedly to avoid the red-green issue. Is that not the case? Gimmetrow 21:25, 25 April 2010 (UTC)
My understanding is the "Yes" and "No" set of templates were made to use "bold" colours, and the "Yes2" and "No2" set of templates were made to use "muted" colors. The proposed green is not quite identical to the "yes" template green, but it looks close to me, and it falls into the "bold" category. Is there any way to have a contrast with muted colours? If one colour must be "bold" to contrast, then is there any point having the other colour muted? Why have the muted forms at all? Gimmetrow 21:23, 1 May 2010 (UTC)
The colour for this need to be changed. It's too similar to Dropped style="background: #FED; vertical-align: middle; text-align: center; " class="dropped table-dropped"|Dropped.
MJaggard (talk) 11:43, 1 July 2010 (UTC)
Is there any rationale at all for colouring all these tables cells? Seems to me that this is all gratuitous ornamentation, a major contributor to the Skittlepedia effect.
These templates offer handy centering of text in cells, and that can be useful. In order for the colouring to remain, a solid rationale is needed per:
If there is a rationale for some cases, then the extant usages need to be pared back significantly.
Cheers, Jack Merridew 06:55, 28 June 2010 (UTC)
In September 2010, a user requested having a place parameter (rather than only "Won"), and allow for gold, silver & bronze. Now, I have added new parameters "place=1" (or: 2, 3, 1st, 2nd, 3rd, gold, silver, bronze) with related colors gold, silver & bronzish, plus new parameters "text=white" and "color=blue" or =#1122CC (etc.) for ribbon colors. See the doc page for listing. In the U.S., a first-place ribbon is typically color blue, but some events mix white and gold ribbons; other cultures favor red for first place ribbons. The Olympics use Gold, Silver and Bronze (for 1/2/3), and some events copy that style.
Inside Template:Won, the expanded markup has added a #switch, only 1 level deeper in expansion depth, with the following logic:
style="background: ((#switch: (({place|Won))} |Won = (({color|#99FF99))} |1|1st|gold |Gold = (({color|Gold))} |2|2nd|silver|Silver = (({color|Silver))} |3|3rd|bronze|Bronze = (({color|#D9A821))} |#default = (({color|#f8eaba))} )); color: (({text|black))}; vertical-align: middle; text-align: (({align|center))}; (({style|))}" class="yes table-yes2"|(({1|(({place|Won))))))
For the #switch of parameter {place|Won}, note how the branches allow count, ordinal and uppercase ("1|1st|gold|Gold"). Each of the 1st, 2nd and 3rd branches set the color, unless parameter {color} is already defined by the user. That logic allows place=1st & color=blue to override the color Gold. Since user-selected colors can be darker, the option text=white (or text=yellow) can improve visibility of the parameter 1 text. Each use of {color} is preceded by " " to allow leading "#" in hex-colors, and avoid the 2010 MediaWiki preprocessor bug which generated newline "1." for # as an auto-numbered line. The 6-character " " is used, instead of <nowiki/>, to avoid the 44-character hidden marker of the nowiki tag, saving 44-6=38 bytes in the internal post-expand size of each "Won" entry. Note the text in parameter place=First can be bolded (with triple-apostrophes), if needed:
Some examples: | |||
{won|place=1st} | 1st | {won|place=First|color=blue) | First |
{won|place=Silver} | Silver | (won|place=First|text=white|color=blue} | First |
{won|place=3|Bronze} | Bronze | {won|place='''First'''|text=white|color=blue} | First |
{won|place=sliver} | sliver | {won|place='''First'''|text=white|color=red} | First |
I do not forsee any major technical problems with these new parameters. They are already listed in the doc page. -Wikid77 10:55, revised 11:14, 16 January 2011 (UTC)
This new addition is messing up ((Infobox musician awards)), for example, in List of awards and nominations received by Leona Lewis all cells for award wins should be green, but they're gold, silver or bronze. AnemoneProjectors 19:27, 22 January 2011 (UTC)
Please add nl:Sjabloon:Tabelcel genomineerd. Thank you - Grashoofd (talk) 22:00, 29 May 2011 (UTC)
91.155.96.165 changed the background color for ((Rh2)) (usually for discontinued softwares) from #edf to #adf, I don't know if this color was chosen ramdomly, maybe he wanted to use the azure to indicate the discontinuity, but on the contrary, it became actually highlighted and focused compared to ((Rh))'s #ececec. So I'm changing it back to #edf. --Tomchen1989 (talk) 03:56, 17 January 2012 (UTC)
Also, Template:Rh2/bgcolor is created to be ((Rh2))'s background color, which is used in ((Rh2)) and can be used in any article for a legend. For example:
*((legend|#ececec|Development status: Current/Active)) *((legend|((Rh2/bgcolor))|Development status: Inactive))
shows
--Tomchen1989 (talk) 04:03, 17 January 2012 (UTC)
Has anyone considered creating a template similar to ((CollegePrimaryHex)) to store some standard colors such as the green that should be used for winning and red for lossing? I know in a number of places different colors are being used for winning and losing such as ((CFB Schedule Entry)), ((CBB schedule entry)), and many more. It would be great to keep this standardized. --ben_b (talk) 19:33, 7 May 2012 (UTC)
Win | Draw | Loss |
Cheers!--EchetusXe 20:47, 7 May 2012 (UTC)
((legend2|#CCFFCC|Win|border=1px solid #AAAAAA)) ((legend2|#FFFFCC|Draw|border=1px solid #AAAAAA)) ((legend2|#FFCCCC|Loss|border=1px solid #AAAAAA)) ((legend2|#CCCCCC|Void|border=1px solid #AAAAAA)) <!-- optional --> ((legend2|#CCCCCC|Postponed|border=1px solid #AAAAAA)) <!-- optional -->
--Walter Görlitz (talk) 04:28, 8 May 2012 (UTC)
Win | Loss | Hex Code (win) | Hex Code (loss) | Article |
---|---|---|---|---|
W 24–17 | L 17–24 | #d0ffe3 | #ffd0e3 | |
W 24–17 | L 17–24 | #ddffdd | #ffdddd | 2011–12 Florida Gators men's basketball team |
W 24–17 | L 17–24 | #ccffcc | #ffcccc | |
W 24–17 | L 17–24 | #cfc | #fcc | 2011–12 Boston Celtics season |
W 24–17 | L 17–24 | #bbffbb | #ffbbbb | 2012 Boston Red Sox season |
W 24–17 | L 17–24 | #bbffbb | #ffbbb0 | 2011 South Carolina Gamecocks baseball team |
W 24–17 | L 17–24 | #D0F0C0 | #FFE6E6 |
These are some combinations that I found on this discussion and on various sports articles. ~ Richmond96 t • c 01:36, 12 May 2012 (UTC)
And maybe we should standartize the colors, that are used in the standaings tables (example). The codes could be the same as win/loss colors. --Edgars2007 (Talk/Contributions) 17:27, 16 May 2012 (UTC)
I've been dealing with these issues and I pretty much used the same hues (dunno about the exact hex codes). Perhaps there could be a separate hex code for OT wins and losses, and forfeits. I previously used quite dark hues but switched to lighter ones. See UAAP Season 73 men's basketball tournament (old and new hues are used) for an example. Other European basketball league season articles also use this but there is no single template. –HTD 00:58, 17 May 2012 (UTC)
The template lacks some interwiki language links, including the romanian ro:Format:Nom -Eb00kie (talk) 18:56, 16 November 2012 (UTC)
The template colour red is a bit disturbing as red signifies a total loss. But nominations should be treated as a honour, not a total loss. Please give it a more neutral colour like yellow.-- Dravidian Hero 00:02, 23 September 2013 (UTC)
See also: User talk:Dsimic § Hack of ((n/a)), and § Merge missing-data templates |
Current look | ? | Unknown |
---|---|---|
Proposal #1 | ? | Unknown |
Proposal #2 | ? | Unknown |
In the last few days Voidxor and I have discussed how ((Dunno))
and ((Unknown))
templates could be made less busy-looking so they produce less distraction when used in more than just a few table cells. A good example of how distractible they can be is available in Nested RAID levels § Comparison, and here are the proposals resulting from our discussion:
((Dunno))
and ((Unknown))
((Dunno))
and ((Unknown))
, made even less busy-looking with <small>...</small>
That way, gray labels would represent "fill me in" cells while black labels should be reserved for the templates producing definitive answers (such as ((Yes))
and ((No))
) that aren't to be filled in later.
Furthermore, ((Dunno))
and ((Unknown))
templates might be merged as they represent pretty much the same thing so having two templates introduces a redundancy. However, having two templates that produce "fill me in" cells with labels of completely different widths might actually be good so the narrow one can be used where the space is tight, and the wide (and more descriptive) one where the space isn't an issue.
Let's discuss, please. — Dsimic (talk | contribs) 07:56, 29 May 2015 (UTC)
<small>
please. — Christoph Päper 22:48, 14 July 2015 (UTC)
<small>...</small>
was proposed because that's how ((n/a))
template does it, so we should probably take that route to ensure consistency between different templates. Another option would be to modify ((n/a))
as well so it uses CSS styling. — Dsimic (talk | contribs) 23:22, 14 July 2015 (UTC)
<small>
being deprecated HTML formatting syntax; we should definitely use CSS instead. – voidxor (talk | contrib) 00:45, 15 July 2015 (UTC)
<span style="font-size: 90%">...</span>
instead, right? — Dsimic (talk | contribs) 00:54, 15 July 2015 (UTC)
<span style="font-size: small;">...</span>
over at Template talk:N/a#Protected edit request on 15 July 2015. That's probably a more direct replacement for the small element than 90%. – voidxor (talk | contrib) 01:11, 15 July 2015 (UTC)
<span style="font-size: smaller;">...</span>
into ((Dunno))
and ((Unknown))
templates. Christoph, I'm a bit confused about the table cell styling you've mentioned; any chances, please, for clarifying that a bit further? — Dsimic (talk | contribs) 09:09, 15 July 2015 (UTC)
<span style="font-size: smaller;">((Unknown))</span>
, instead of changing the font size for the template as a whole. Personally, I'd regard that as a workaround, and am more inclined to modify the templates consistently across all articles, but that's just my two cents. – voidxor (talk | contrib) 19:22, 15 July 2015 (UTC)
span
element when you can put font-size:small
into an existing style
attribute, i.e. the one for the table cell setting background color etc. — Christoph Päper 22:11, 15 July 2015 (UTC)
|style=
parameter in these templates. So now that we have input from presumably all interested parties, what have we decided to do? Gray text? Smaller text size? Merge? – voidxor (talk | contrib) 22:24, 15 July 2015 (UTC)
((n/a))
template in which the <span>
element is pretty much redundant; Voidxor, would you prefer to create another protected template edit request on ((n/a))
, just because you've already created one? Speaking of the next steps on ((Dunno))
and ((Unknown))
templates, IMHO we should go with font-size: small;
CSS styling and gray text for now (proposal #2), and leave it so for a week or two before deciding on the merger. That way, more people will be able to see this whole discussion, which should be a good thing before the merger. — Dsimic (talk | contribs) 03:28, 16 July 2015 (UTC)
smaller
rather than small
, though. – voidxor (talk | contrib) 20:05, 16 July 2015 (UTC)I was wondering, since there is a template for "shortlisted", should there be one for "longlisted"? For example, in List of awards and nominations received by EastEnders, taking the National Television Awards as an example, a longlist is released, then the public votes and there's a shortlist. I'm currently using "nominated" for those that don't make the shortlist, but I think if there was a "longlisted" option, it would mean less confusion as to what everything actually means. –AnemoneProjectors– 09:57, 24 January 2013 (UTC)
((Dunno))
use said parameter in order to maintain existing short labels in tables pressed for space. – voidxor 21:09, 18 April 2016 (UTC)((Dunno))
and ((Unknown))
templates might be merged as they represent pretty much the same thing so having two templates introduces a redundancy. However, having two templates that produce "fill me in" cells with labels of completely different widths might actually be good so the narrow one can be used where the space is tight, and the wide (and more descriptive) one where the space isn't an issue.
Let's discuss, please. — Dsimic (talk | contribs) 07:56, 29 May 2015 (UTC)
table-unknown
CSS class, whereas ((N/a)) and ((BLACK)) both belong the the table-na
class. Thus, I think ((N/a)) is more geared toward cases where the information can never be known (see also, n/a). – voidxor (talk | contrib) 21:13, 16 July 2015 (UTC)((Dunno))
and ((Unknown))
is quite confusing. We should have one template (which should be ((Unknown))
) for the cells that are to be filled in by someone at some point in time, and the other template (which is ((n/a))
) for the cells that aren't applicable and shouldn't ever be filled in. Another option for the ((Dunno))
→ ((Unknown))
merger might be to introduce a template parameter to the destination template that would allow a selection between the long and short labels ("?" vs. "Unknown"). Oh, and I'm more geared toward gray letters. — Dsimic (talk | contribs) 01:18, 17 July 2015 (UTC)
((Dunno))
and ((Unknown))
were created for different size cells, why do their background colors differ?! It makes no sense. A shorter version of a template should only vary by the text label, not the color scheme nor font size. – voidxor (talk | contrib) 03:19, 17 July 2015 (UTC)
((Unknown))
, depending on the way it's transcluded; as a result, we'd have zero disturbance to already existing tables, in case one of the templates has been selected specifically for its label length. — Dsimic (talk | contribs) 04:56, 17 July 2015 (UTC)
((Unknown|small=yes))
, instead of doing a redirect. – voidxor (talk | contrib) 20:31, 17 July 2015 (UTC)
((Unknown))
is used in a "cannot be known" capacity? Perhaps we should spot check the transclusions list. – voidxor 17:44, 26 August 2015 (UTC)This template is not documented in Template:Table cell templates/doc. 80.221.159.67 (talk) 15:54, 31 August 2016 (UTC)
It looks red on articles. It looks like a fail. It should be changed. Maybe a very light blue or a slightly lightened purple colour. The redder colours are conventionally to highlight a failure(/), that you got burned by the embers, but nominated is lifted to the circle. Actually, maybe a lighter green than Template:Won would look much better lined up beside each other. Thanks o/ ~ R.T.G 17:46, 15 October 2019 (UTC)
Notice: of ongoing dicussion at Wikipedia:Village_pump_(proposals)#The_colour_of_nomination ~ R.T.G 20:12, 20 October 2019 (UTC)
Hi, GermanJoe, I thought I'd match the style of ((ya)) and ((na)). Currently, it doesn't match any other set of table cell templates. Cheers. Guarapiranga (talk) 20:08, 29 October 2019 (UTC)
(Moved from redirect page Template talk:Dunno. GermanJoe (talk) 20:12, 29 October 2019 (UTC))
Hi, the templates ((N/a)) ((Rh)) ((CNone)) ((Varies)) ((Non-album single)) ((Unreleased)) ((Dunno)) are all using a gray what looks first like the wikitable-header-gray #eaecf0 but IT IS NOT the wikitable gray. Why not adapting both colours to each other? I mean: changing the templates from #ececec to #eaecf0?
#eaecf0 | |||||||
---|---|---|---|---|---|---|---|
#ececec | — | Rh | CNone | Varies | Non-album single | Unreleased | ? |
Best Regards, --W like wiki good to know 00:15, 31 October 2019 (UTC)
By the way: why templates ((Unreleased)) is sometimes working sometimes not, for example here:
#eaecf0 | |||||||
---|---|---|---|---|---|---|---|
#ececec | — | Rh | CNone | Varies | Non-album single | data-sort-value="" style="background: #ececec; color: #2C2C2C; vertical-align: middle; text-align: center; " class="table-na" | Unreleased | ? |
Thx for that too!! --W like wiki good to know 00:37, 31 October 2019 (UTC)
This edit request to Template:Rh has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Add "| Row Header" at the end of the 3rd ligne to display the template instead of its code. Kebaab (talk) 14:46, 12 February 2020 (UTC)
scope="row"
added to them. — Christoph Päper 09:55, 27 February 2020 (UTC)
This edit request to Template:Won has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please change the 2nd place color to a lighter gray and the 3rd place color to brownish-yellow. Thanks! HappyMeal189 (talk) 21:30, 19 July 2021 (UTC)
((edit template-protected))
template. firefly ( t · c ) 21:49, 19 July 2021 (UTC)