![]() | This 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. |
Archive 1 | Archive 2 | Archive 3 | → | Archive 5 |
Please replace the ".Merge" and ".Merge td" styles with this code. Basically, this was mistakenly added as a "class", rather than an "id". Note that in this CSS, disambig and spoiler are done as id, so this change is consistent. Perhaps you could also group those template styles together so they are easier to see.
(code removed for space)
Let me know when this is complete, so I can correct the related templates quickly. -- Netoholic @ 21:22, 13 July 2005 (UTC)
I'm running Firefox 1.0.4 on Windows, using Monobook, and the boxes have completely disappeared. IE displays them. Has this been tested with Firefox? If not, why not? If so, why am I not seeing any boxes anymore? JRM · Talk 12:31, 17 July 2005 (UTC)
It's nice that the skins now don't get out of sync. However, this happens at the expense of the commonly-styled items looking rather out of place in every single one (or, at best, all but one) of the skins. What we really want is a set of classes that are defined in each skin seperately, but which all skins have (a CSS interface class, as it were). This CSS should be used sparingly, and not for proper styling of meta-data like structures, which semantically should be more part of the "overview" of the article than the article itself - that is, they should be styled to look like the rest of the skin. A notable area where common CSS rather than skin-specific CSS would be a bad idea is for infoboxes - it should blend in with the skin (and I strongly doubt that there is a way of styling such a highly-styled item so that it blends with all skins, or even more than one, really).
James F. (talk) 11:38, 23 July 2005 (UTC)
We seemed to have complete ignored the discussion about class names from monobook.css: ( ed g2s • talk 15:36, 8 August 2005 (UTC))
table.pretty { ... }
with #content table { ... }
). I can't see any other problems with implementing it.
ed g2s •
talk
12:59, 24 July 2005 (UTC)In the German wikipedia I've added empty-cells:show;
to the
prettytable template. With it, adding " " or using other ugly tricks to get borders around all cells is unnecessary. My suggestion would be adding it to the "prettytable" class (or whatever it's name ends up to be), would be good as well. And yes, I know it won't work on older browsers. BTW, I stumbled upon the issue again, when looking at the article
Comparison of accounting software in it's version (
http://en.wikipedia.org/?title=Comparison_of_accounting_software&oldid=20546718). For "normal" users, I'd assume it's a big help. --
S.K.
19:23, 8 August 2005 (UTC)
For the last half year, there has been discussions (see Prettytable and Monobook.css) regarding the Prettytable template, a "cute design template for tables" currently used by almost 4,000 wiki-pages – that's hard work for the servers, :-(
It has been suggested to create a new table class, for example pretty or prettytable (which is actually already in use in Common.css), but it has been suggested (by myself) to simply change the CSS for tables in general. The proposed CSS follows (thanks to User:Crissov):
table { margin: 1em 1em 1em 0; border-collapse: collapse; background: #f9f9f9; color: #000; empty-cells:show; /* font-size: 95%;*/ } table th, table td { border: 1px #aaa solid; padding: 4px; } table th[scope="col"], /* column header */ table>tbody>tr:first-child>th, table th[scope="row"], /* row header */ table>tbody>tr>th:first-child { background-color: #ccccff; } table th[scope="row"], /* row header */ table>tbody>tr>th:first-child { text-align: left; } table>tbody>tr:hover>td, table>tbody>tr>td:hover {/* or '*' instead of 'td' */ background-color: #e0e0ff; }
I see the following possible problems:
Please give me your thoughts. Regards, Fred Bradstadt 16:09, August 20, 2005 (UTC)
div#bodyContent table { margin: 1em 1em 1em 0; border-collapse: collapse; background: #f9f9f9; color: #000000; empty-cells: show; /* font-size: 95%;*/ } div#bodyContent table th, div#bodyContent table td { border: 1px #aaa solid; padding: 4px; } div#bodyContent table th[scope="col"], /* column header */ div#bodyContent table>tbody>tr:first-child>th, div#bodyContent table th[scope="row"], /* row header */ div#bodyContent table>tbody>tr>th:first-child { background-color: #ccccff; } div#bodyContent table th[scope="row"], /* row header */ div#bodyContent table>tbody>tr>th:first-child { text-align: left; } div#bodyContent table>tbody>tr:hover>td, div#bodyContent table>tbody>tr>td:hover {/* or '*' instead of 'td' */ background-color: #e9e9ff; }
div#bodyContent table.right {margin: 0 1em 1em 1em;} div#bodyContent table.center {margin: 1em auto;}
class="template"
kind of thing? By the way, many templates use the toccolours
class.The current class "prettytable" gives results quite different from the template "prettytable". The proposal above gives good results in a few summary tests I did (in IE6). Would it be possible to take the proposed style above already in production as a class "prettytable" (or should we rename to "wikitable")? Then we can experiment with replacing the various "prettysomething" templates already in use. See also remarks at Template talk:Prettytable. Merging the style with an additional style parameter at the table itself works well. − Woodstone 20:19:25, 2005-09-08 (UTC)
Cellpadding doesn't work:
Prettytable template | template | template |
---|---|---|
100 | Cake | Monster in the closet |
Wikipedia | ^______^ | Darth Vader |
Moo | 1.618033989 | Pay your bills |
Prettytable class | class | class |
---|---|---|
100 | Cake | Monster in the closet |
Wikipedia | ^______^ | Darth Vader |
Moo | 1.618033989 | Pay your bills |
Otherwise it looks good to me. Should be tried with many different tables and see if they all look good. — Omegatron 16:02, September 9, 2005 (UTC)
Moved this thread from User talk:Lexor on 11:48, September 8, 2005 (UTC)
Hmmm. Why did you do this? First, I think there should be semicolons after "display : none ! important;", and second, plainlinksneverexpand should never expand links, whether in print or on screen... Lupo 09:13, September 8, 2005 (UTC)
.plainlinksneverexpand a.external.text:after { display: none !important }
Currently the Template:Prettytable and the style Prettytable give quite different results. Discussions have been ongoing on this and other pages. The proposal below is a simple version that embodies most comments made. It comes so close to the original template that most likely no disturbance of layouts will occur. A few small tweaks are:
table.wikitable { margin: 1em 1em 1em 0; background-color: #f9f9f9; border: 1px solid #aaaaaa; border-collapse: collapse; empty-cells: show; } table.wikitable th { padding: 0.2em; border: 1px solid #dfdfdf; background-color: #efefef; text-align: center; } table.wikitable td { padding: 0.2em; border: 1px solid #dfdfdf; }
Who would be able to add this to the protected page? After that is done, we can replace several templates (which are not so consistenty named right now):
− Woodstone 23:01:59, 2005-09-10 (UTC)
The original one started out as 95%; that's why there is a 100 version; the 95 version came about because people got tired of the edit war, never knowing what size was in. In my new proposed class the font size is not specified. So it can be decided locally at the table if a reduction or enlargement is needed. I changed the example table to avoid that the table size is influenced by the text of the format option. − Woodstone 09:37:04, 2005-09-11 (UTC)
Thanks for adding it. I agree "wiki" is a rather presumptuous class. I have no objection against "prettytable", but during testing, it might disturb existing articles. I propose to weaken the class name to "wikitable" for the time being. I already tested a number of previews, and it gives quite good results so far. One thing that was not right yet, were the nicely faint internal borders of the template. I have experimented and come up with an adapted version. On my IE6 the "empty-cells:show" does not seem to work however. Could you please replace this version for further testing? Hopefully the edit war over font size at template:prettytable can be ended when the style is established. − Woodstone 09:37:04, 2005-09-11 (UTC)
table.wikitable { margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaaaaa solid; border-collapse: collapse; } table.wikitable th { border: 1px #aaaaaa solid; padding: 0.2em; background: #efefef; text-align: center; } table.wikitable td { border: 1px #aaaaaa solid; padding: 0.2em; }
x | y | z | |
---|---|---|---|
blank | |||
primary | red | green | blue |
mixed | cyan | magenta | yellow |
neutral | dk grey | lt grey | white |
empty |
x | y | z | |
---|---|---|---|
blank | |||
primary | red | green | blue |
mixed | cyan | magenta | yellow |
neutral | dk grey | lt grey | white |
empty |
x | y | z | |
---|---|---|---|
blank | |||
primary | red | green | blue |
mixed | cyan | magenta | yellow |
neutral | dk grey | lt grey | white |
empty |
x | y | z | |
---|---|---|---|
blank | |||
primary | red | green | blue |
mixed | cyan | magenta | yellow |
neutral | dk grey | lt grey | white |
empty |
Header | Foo | Bar |
---|---|---|
old {{ prettytable}} | ||
100 | Cake | Monster in the closet |
Wikipedia | ^______^ | Darth Vader |
Moo | 1.618033989 | Pay your bills |
Header | Foo | Bar |
---|---|---|
class="prettytable" | ||
100 | Cake | Monster in the closet |
Wikipedia | ^______^ | Darth Vader |
Moo | 1.618033989 | Pay your bills |
Header | Foo | Bar |
---|---|---|
class="wikitable" | ||
100 | Cake | Monster in the closet |
Wikipedia | ^______^ | Darth Vader |
Moo | 1.618033989 | Pay your bills |
On my IE6 I have clearly single pixel dark outer and faint inner borders. I see this also in many "infobox" templates (like for countries). How do you see those? Strangely enough, if I copy the prettytable template content in a local file, it looks different (grey inner borders) than via wikipedia (almost white inner borders). There must be other styles influencing behaviour. How do you see them above here? The amount of faintness can of course be discussed and determined to be perceptable for most users. Faint inner borders look much more distinguished than all borders heavy. After a few trials I find #dfdfdf to be about equal to the color in inner borders of the infoboxes. I agree with yourt proposal above for #efefef as header background. I changed my list above accordingly. I tried a 2-pixel border, but it is quite ugly and out if style with the rest of wikipedia. − Woodstone 21:31:33, 2005-09-12 (UTC)
table.wikitable th {
border: 1px #f9f9f9 solid; padding: 0.2em; background: #f2f2f2; text-align: center;
} table.wikitable td {
border: 1px #efefef solid; padding: 0.2em;
}
table.wikitable th, table.wikitable td {
border: 1px #aaaaaa solid; padding: 0.2em;
} table.wikitable th {
background: #f2f2f2; text-align: center;
}
It looks good, but it's a pity that we cannot do the faint inner borders. As for clarity of definition I would prefer a full split between th and td parts. The replacement of template:prettytable100center was incorrect (now ok). As for margin (see remark below), we might include only top and bottom margin. That would work for many cases of left and right placement, where text does not flow around. With flow-around margin can still be added locally by margin-right="0.2em". − Woodstone 20:19, 15 September 2005 (UTC)
.wikitable should not define margins in the main class. There should be sub-classes, wRight, wLeft and wCenter, as the margins are dependent on table alignment. ed g2s • talk 14:32, 15 September 2005 (UTC)
I agree. In particular, the top margin must be set to 0; otherwise, table captions will be separated from their table by this margin. The margins also cannot be overridden in user CSS.
‣ᓛᖁ
ᑐ
18:14, 19 September 2005 (UTC)
Padding is too small and text is too large. It looks strange. Either increase the padding, or decrease the font size. Thanks. — Cantus… ☎ 06:28, 16 September 2005 (UTC)
Sure:
— Cantus… ☎ 00:31, 18 September 2005 (UTC)
Indeed your padding looks a tiny bit smaller than what I see. I tested locally to set padding to 0.25em and it exactly replicates the original size of the template (at the default font in my IE6). However there were requests to make padding a trifle smaller. What does everyone think, should we try 0.25? − Woodstone 18:06, 19 September 2005 (UTC)
Just a little bit more padding, please. The current padding sets a separation that is even less than a space character! — Cantus… ☎ 23:24, 21 September 2005 (UTC)
I would like to request that we consider accessibility as a priority. Moving to a stylesheet is probably a 'good thing' for accessibility.
However, there are still some features within the proposed standard style that could be improved. For example, the colours reduce contrast. It would improve access if contrast between text and background were increased.
People may also wish to check example pages with: http://valet.webthing.com/access/url.html
Many thanks. Bobblewik 14:14, 20 September 2005 (UTC)
I like the captions of the prettytable template better; at the bottom of the table and bolded. What do others think? — Omegatron 18:01, 21 September 2005 (UTC)
It is often required that row header cells are not centered. With the old template:prettytable this worked by adding align="left". However, with the class "wikitable" this does not seem to work anymore. Adding style="text-align: left" still works. See examples here:
appearance rowheader | extra formatting in rowheader | comment |
---|---|---|
r1 | none | header centered as per style |
r2 | align="left" | straight override not working |
r3 | style="text-align: left" | style override working |
A few articles currently suffer from this effect. Can someone explain why straight alignment does not override the stylesheet? Is it conforming css specs? − Woodstone 21:43, 25 September 2005 (UTC)
th
s, i.e. something like.wikitable th:first-child {text-align: left;} .wikitable tr:first-child th {text-align: center;}
>
) to result in fewer false positives (possible with nested tables), but would probably work in fewer browsers, esp. Internet Explorer. (IIRC IE6 supports :first-child
, otherwise the point is moot.)Since a few weeks the class "wikitable" has been in use to implement the various templates {{ prettytable}}. It seems to be working fine. However during experimentation phase a class "prettytable" was added to the Common.css stylesheet as well. Now the time has come to eliminate one of the names.
− Woodstone 10:09, 5 October 2005 (UTC)
This page is now imported directly into the HTML for all skins. The @import lines can be removed from all the skin-specific CSS pages, after a few days have elapsed for cache expiry. -- Tim Starling 10:55, 23 October 2005 (UTC)
I'm shortly going to add a little bit of CSS to this file for the proposed new Main Page design. This is for testing purposes only, to check if this design works correctly live on Wikipedia. It will not alter the display of the live site. Please don't remove it for the moment. Thanks, Tom- 23:19, 25 October 2005 (UTC)
The hardcoded css for monobook at http://en.wikipedia.org/skins-1.5/monobook/main.css includes the lines:
img { border: none; vertical-align: middle; }
Classic, Nostalgia, Cologne Blue, and I suspect most of the new skins do not, and where this is not taken into account, the results look horrible. (See, for example, Template:Mac-stub, where the once-standard table code still visible in Template:Metapicstub was recently removed.) Rather than quixotically searching through the template namespace and adding tables to control this visual issue (usually a poor idea), with confused monobook users following me and breaking them again, can this be added here? — Cryptic (talk) 06:30, 28 October 2005 (UTC)
div#bodyContent img { border: none; vertical-align: middle; }
Hi guys, I have my own website running on the wiki software and I am beating my brain trying to figure out how to get rid of the external link arrow on my reference template. I've got what seems to be all the pieces needed in the default skin's Summabook.css file, as well as monobook's Monobook.css. And for good measure, it's in Common.css (even though I don't import it into the other .css files like wikipedia does) and the main.css file for the skin. How can it not be loading the code and getting rid of the arrows? What's missing? David Bergan 07:18, 1 November 2005 (UTC)
#bodyContent a[href^=http://], #bodyContent a[href^=gopher://] {background-image:url(external.png)}
Would anyone object to removing text-align: justify
from .notice and .messagebox? This serves no purpose, except to add big ugly gaps between the words and make it looks like it belongs to some other web site. —
Michael
Z. 2005-11-15 19:30 Z
I originally reported this here, not knowing where else to post it. I filed a bug and was referred here, so here's the original message, somewhat redacted:
There are two problems with the Common stylesheet that should be fixed ASAP. First, the filter statement on line 225 should simply be removed: It is nonstandard and produces errors messages in Firefox's debugging console. Secondly, the line-height property on line 208 has no units (should be 1.5em, I'm sure), which is invalid and also causes error messages. — HorsePunchKid→ 龜 19:36, 18 November 2005 (UTC)
y with macron, ȳ, Unicode 233 hex, which is used in Old English morphology, appears as a box on my computer even though it is enclosed in Template Unicode. The same problem occurs with Template IPA: ȳ
I use MSIE 6.0, and my fonts include Arial Unicode MS, Microsoft Sans Serif.
The problem appears to be that Arial Unicode MS appears before Microsoft Sans Serif in MediaWiki:Common.css, but Arial Unicode MS doesn't support codes 218-24F. I propose that the order of these two fonts be reversed. -- teb728 01:31, 3 December 2005 (UTC)
The contrast in wikitable is unnecessarily low. Can we increase it please? Bobblewik 12:33, 14 November 2005 (UTC)
T-34 Model 1940 | T-34 Model 1941 | T-34 Model 1942 | T-34 Model 1943 | T-34-85 | T-44 | |
---|---|---|---|---|---|---|
Weight | 26 t | 26.5 t | 28.5 t | 30.9 t | 32 t | 31.9 t |
Gun | 76.2mm L-11 | 76.2mm F-34 | 76.2mm F-34 | 76.2mm F-34 | 85mm ZiS-S-53 | 85mm ZiS-S-53 |
Ammunition | 76 rounds | 77 rounds | 77 rounds | 100 rounds | 60 rounds | 58 rounds |
Fuel | 460 L | 460 L | 610 L | 790 L | 810 L | 642 L |
Road range | 300 km | 400 km | 400 km | 465 km | 360 km | 300 km |
Armour | 15–45 mm | 20–52 mm | 20–65 mm | 20–70 mm | 20–90 mm | 15–120 mm |
Cost | 270,000 rubles | 193,000 rubles | 135,000 rubles | 164,000 rubles |
[removed wikitable version with right-aligned numbers; the version below is better —
Michael
Z. 2005-12-7 21:45 Z]
I definitely find the second one easier to read. But you misunderstood one thing I said. Centering is disadvised when "no horizontal rules" are present. Since wikitable has rules (and within the columns dimensions are unequal) the numbers could have stayed centered. My preference would be like below. (Note that the original smaller characters also reduced legibility.) − Woodstone 21:28, 7 December 2005 (UTC)
T-34 Model 1940 |
T-34 Model 1941 |
T-34 Model 1942 |
T-34 Model 1943 |
T-34-85 | T-44 | |
---|---|---|---|---|---|---|
Weight (tonnes) | 26 | 26.5 | 28.5 | 30.9 | 32 | 31.9 |
Gun | 76.2mm L-11 | 76.2mm F-34 | 76.2mm F-34 | 76.2mm F-34 | 85mm ZiS-S-53 | 85mm ZiS-S-53 |
Ammunition (rounds) | 76 | 77 | 77 | 100 | 60 | 58 |
Fuel (litres) | 460 | 460 | 610 | 790 | 810 | 642 |
Road range (km) | 300 | 400 | 400 | 465 | 360 | 300 |
Armour (mm) | 15–45 | 20–52 | 20–65 | 20–70 | 20–90 | 15–120 |
Cost (rubles) | 270,000 | 193,000 | 135,000 | 164,000 |
It ain't working! When I print, it expands the external URLs. This is having a major effect in a few template:
Can someone fix this? - Ta bu shi da yu 08:08, 5 December 2005 (UTC)
Since a large portion of people are color blind in some sense, we should address this quickly:
(copied from User talk:Jimbo Wales)
— BRIAN 0918 • 2005-12-8 00:04
Please change .infobox.sisterproject to be "width: 20em", which matches more closely how these were originally (which was 250px, but em is better). -- Netoholic @ 14:23, 15 December 2005 (UTC)
Seeing the edit http://en.wikipedia.org/?title=List_of_The_Simpsons_episodes&diff=31567503&oldid=31556419 – where a hard-coded color is applied to every 2nd table row – earlier today made me think: "we need a standard color for highlighting stuff/text/table rows". How about adding
table.wikitable .highlight, table.prettytable .highlight { background: #ececf6; }
to this CSS. Then we might simply use
{| class="wikitable" |- | one row || one row |- class="highlight" | another || another row |}
instead of the hardcoded colors? -- Fred Bradstadt 08:39, 16 December 2005 (UTC)
![]() | This 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. |
Archive 1 | Archive 2 | Archive 3 | → | Archive 5 |
Please replace the ".Merge" and ".Merge td" styles with this code. Basically, this was mistakenly added as a "class", rather than an "id". Note that in this CSS, disambig and spoiler are done as id, so this change is consistent. Perhaps you could also group those template styles together so they are easier to see.
(code removed for space)
Let me know when this is complete, so I can correct the related templates quickly. -- Netoholic @ 21:22, 13 July 2005 (UTC)
I'm running Firefox 1.0.4 on Windows, using Monobook, and the boxes have completely disappeared. IE displays them. Has this been tested with Firefox? If not, why not? If so, why am I not seeing any boxes anymore? JRM · Talk 12:31, 17 July 2005 (UTC)
It's nice that the skins now don't get out of sync. However, this happens at the expense of the commonly-styled items looking rather out of place in every single one (or, at best, all but one) of the skins. What we really want is a set of classes that are defined in each skin seperately, but which all skins have (a CSS interface class, as it were). This CSS should be used sparingly, and not for proper styling of meta-data like structures, which semantically should be more part of the "overview" of the article than the article itself - that is, they should be styled to look like the rest of the skin. A notable area where common CSS rather than skin-specific CSS would be a bad idea is for infoboxes - it should blend in with the skin (and I strongly doubt that there is a way of styling such a highly-styled item so that it blends with all skins, or even more than one, really).
James F. (talk) 11:38, 23 July 2005 (UTC)
We seemed to have complete ignored the discussion about class names from monobook.css: ( ed g2s • talk 15:36, 8 August 2005 (UTC))
table.pretty { ... }
with #content table { ... }
). I can't see any other problems with implementing it.
ed g2s •
talk
12:59, 24 July 2005 (UTC)In the German wikipedia I've added empty-cells:show;
to the
prettytable template. With it, adding " " or using other ugly tricks to get borders around all cells is unnecessary. My suggestion would be adding it to the "prettytable" class (or whatever it's name ends up to be), would be good as well. And yes, I know it won't work on older browsers. BTW, I stumbled upon the issue again, when looking at the article
Comparison of accounting software in it's version (
http://en.wikipedia.org/?title=Comparison_of_accounting_software&oldid=20546718). For "normal" users, I'd assume it's a big help. --
S.K.
19:23, 8 August 2005 (UTC)
For the last half year, there has been discussions (see Prettytable and Monobook.css) regarding the Prettytable template, a "cute design template for tables" currently used by almost 4,000 wiki-pages – that's hard work for the servers, :-(
It has been suggested to create a new table class, for example pretty or prettytable (which is actually already in use in Common.css), but it has been suggested (by myself) to simply change the CSS for tables in general. The proposed CSS follows (thanks to User:Crissov):
table { margin: 1em 1em 1em 0; border-collapse: collapse; background: #f9f9f9; color: #000; empty-cells:show; /* font-size: 95%;*/ } table th, table td { border: 1px #aaa solid; padding: 4px; } table th[scope="col"], /* column header */ table>tbody>tr:first-child>th, table th[scope="row"], /* row header */ table>tbody>tr>th:first-child { background-color: #ccccff; } table th[scope="row"], /* row header */ table>tbody>tr>th:first-child { text-align: left; } table>tbody>tr:hover>td, table>tbody>tr>td:hover {/* or '*' instead of 'td' */ background-color: #e0e0ff; }
I see the following possible problems:
Please give me your thoughts. Regards, Fred Bradstadt 16:09, August 20, 2005 (UTC)
div#bodyContent table { margin: 1em 1em 1em 0; border-collapse: collapse; background: #f9f9f9; color: #000000; empty-cells: show; /* font-size: 95%;*/ } div#bodyContent table th, div#bodyContent table td { border: 1px #aaa solid; padding: 4px; } div#bodyContent table th[scope="col"], /* column header */ div#bodyContent table>tbody>tr:first-child>th, div#bodyContent table th[scope="row"], /* row header */ div#bodyContent table>tbody>tr>th:first-child { background-color: #ccccff; } div#bodyContent table th[scope="row"], /* row header */ div#bodyContent table>tbody>tr>th:first-child { text-align: left; } div#bodyContent table>tbody>tr:hover>td, div#bodyContent table>tbody>tr>td:hover {/* or '*' instead of 'td' */ background-color: #e9e9ff; }
div#bodyContent table.right {margin: 0 1em 1em 1em;} div#bodyContent table.center {margin: 1em auto;}
class="template"
kind of thing? By the way, many templates use the toccolours
class.The current class "prettytable" gives results quite different from the template "prettytable". The proposal above gives good results in a few summary tests I did (in IE6). Would it be possible to take the proposed style above already in production as a class "prettytable" (or should we rename to "wikitable")? Then we can experiment with replacing the various "prettysomething" templates already in use. See also remarks at Template talk:Prettytable. Merging the style with an additional style parameter at the table itself works well. − Woodstone 20:19:25, 2005-09-08 (UTC)
Cellpadding doesn't work:
Prettytable template | template | template |
---|---|---|
100 | Cake | Monster in the closet |
Wikipedia | ^______^ | Darth Vader |
Moo | 1.618033989 | Pay your bills |
Prettytable class | class | class |
---|---|---|
100 | Cake | Monster in the closet |
Wikipedia | ^______^ | Darth Vader |
Moo | 1.618033989 | Pay your bills |
Otherwise it looks good to me. Should be tried with many different tables and see if they all look good. — Omegatron 16:02, September 9, 2005 (UTC)
Moved this thread from User talk:Lexor on 11:48, September 8, 2005 (UTC)
Hmmm. Why did you do this? First, I think there should be semicolons after "display : none ! important;", and second, plainlinksneverexpand should never expand links, whether in print or on screen... Lupo 09:13, September 8, 2005 (UTC)
.plainlinksneverexpand a.external.text:after { display: none !important }
Currently the Template:Prettytable and the style Prettytable give quite different results. Discussions have been ongoing on this and other pages. The proposal below is a simple version that embodies most comments made. It comes so close to the original template that most likely no disturbance of layouts will occur. A few small tweaks are:
table.wikitable { margin: 1em 1em 1em 0; background-color: #f9f9f9; border: 1px solid #aaaaaa; border-collapse: collapse; empty-cells: show; } table.wikitable th { padding: 0.2em; border: 1px solid #dfdfdf; background-color: #efefef; text-align: center; } table.wikitable td { padding: 0.2em; border: 1px solid #dfdfdf; }
Who would be able to add this to the protected page? After that is done, we can replace several templates (which are not so consistenty named right now):
− Woodstone 23:01:59, 2005-09-10 (UTC)
The original one started out as 95%; that's why there is a 100 version; the 95 version came about because people got tired of the edit war, never knowing what size was in. In my new proposed class the font size is not specified. So it can be decided locally at the table if a reduction or enlargement is needed. I changed the example table to avoid that the table size is influenced by the text of the format option. − Woodstone 09:37:04, 2005-09-11 (UTC)
Thanks for adding it. I agree "wiki" is a rather presumptuous class. I have no objection against "prettytable", but during testing, it might disturb existing articles. I propose to weaken the class name to "wikitable" for the time being. I already tested a number of previews, and it gives quite good results so far. One thing that was not right yet, were the nicely faint internal borders of the template. I have experimented and come up with an adapted version. On my IE6 the "empty-cells:show" does not seem to work however. Could you please replace this version for further testing? Hopefully the edit war over font size at template:prettytable can be ended when the style is established. − Woodstone 09:37:04, 2005-09-11 (UTC)
table.wikitable { margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaaaaa solid; border-collapse: collapse; } table.wikitable th { border: 1px #aaaaaa solid; padding: 0.2em; background: #efefef; text-align: center; } table.wikitable td { border: 1px #aaaaaa solid; padding: 0.2em; }
x | y | z | |
---|---|---|---|
blank | |||
primary | red | green | blue |
mixed | cyan | magenta | yellow |
neutral | dk grey | lt grey | white |
empty |
x | y | z | |
---|---|---|---|
blank | |||
primary | red | green | blue |
mixed | cyan | magenta | yellow |
neutral | dk grey | lt grey | white |
empty |
x | y | z | |
---|---|---|---|
blank | |||
primary | red | green | blue |
mixed | cyan | magenta | yellow |
neutral | dk grey | lt grey | white |
empty |
x | y | z | |
---|---|---|---|
blank | |||
primary | red | green | blue |
mixed | cyan | magenta | yellow |
neutral | dk grey | lt grey | white |
empty |
Header | Foo | Bar |
---|---|---|
old {{ prettytable}} | ||
100 | Cake | Monster in the closet |
Wikipedia | ^______^ | Darth Vader |
Moo | 1.618033989 | Pay your bills |
Header | Foo | Bar |
---|---|---|
class="prettytable" | ||
100 | Cake | Monster in the closet |
Wikipedia | ^______^ | Darth Vader |
Moo | 1.618033989 | Pay your bills |
Header | Foo | Bar |
---|---|---|
class="wikitable" | ||
100 | Cake | Monster in the closet |
Wikipedia | ^______^ | Darth Vader |
Moo | 1.618033989 | Pay your bills |
On my IE6 I have clearly single pixel dark outer and faint inner borders. I see this also in many "infobox" templates (like for countries). How do you see those? Strangely enough, if I copy the prettytable template content in a local file, it looks different (grey inner borders) than via wikipedia (almost white inner borders). There must be other styles influencing behaviour. How do you see them above here? The amount of faintness can of course be discussed and determined to be perceptable for most users. Faint inner borders look much more distinguished than all borders heavy. After a few trials I find #dfdfdf to be about equal to the color in inner borders of the infoboxes. I agree with yourt proposal above for #efefef as header background. I changed my list above accordingly. I tried a 2-pixel border, but it is quite ugly and out if style with the rest of wikipedia. − Woodstone 21:31:33, 2005-09-12 (UTC)
table.wikitable th {
border: 1px #f9f9f9 solid; padding: 0.2em; background: #f2f2f2; text-align: center;
} table.wikitable td {
border: 1px #efefef solid; padding: 0.2em;
}
table.wikitable th, table.wikitable td {
border: 1px #aaaaaa solid; padding: 0.2em;
} table.wikitable th {
background: #f2f2f2; text-align: center;
}
It looks good, but it's a pity that we cannot do the faint inner borders. As for clarity of definition I would prefer a full split between th and td parts. The replacement of template:prettytable100center was incorrect (now ok). As for margin (see remark below), we might include only top and bottom margin. That would work for many cases of left and right placement, where text does not flow around. With flow-around margin can still be added locally by margin-right="0.2em". − Woodstone 20:19, 15 September 2005 (UTC)
.wikitable should not define margins in the main class. There should be sub-classes, wRight, wLeft and wCenter, as the margins are dependent on table alignment. ed g2s • talk 14:32, 15 September 2005 (UTC)
I agree. In particular, the top margin must be set to 0; otherwise, table captions will be separated from their table by this margin. The margins also cannot be overridden in user CSS.
‣ᓛᖁ
ᑐ
18:14, 19 September 2005 (UTC)
Padding is too small and text is too large. It looks strange. Either increase the padding, or decrease the font size. Thanks. — Cantus… ☎ 06:28, 16 September 2005 (UTC)
Sure:
— Cantus… ☎ 00:31, 18 September 2005 (UTC)
Indeed your padding looks a tiny bit smaller than what I see. I tested locally to set padding to 0.25em and it exactly replicates the original size of the template (at the default font in my IE6). However there were requests to make padding a trifle smaller. What does everyone think, should we try 0.25? − Woodstone 18:06, 19 September 2005 (UTC)
Just a little bit more padding, please. The current padding sets a separation that is even less than a space character! — Cantus… ☎ 23:24, 21 September 2005 (UTC)
I would like to request that we consider accessibility as a priority. Moving to a stylesheet is probably a 'good thing' for accessibility.
However, there are still some features within the proposed standard style that could be improved. For example, the colours reduce contrast. It would improve access if contrast between text and background were increased.
People may also wish to check example pages with: http://valet.webthing.com/access/url.html
Many thanks. Bobblewik 14:14, 20 September 2005 (UTC)
I like the captions of the prettytable template better; at the bottom of the table and bolded. What do others think? — Omegatron 18:01, 21 September 2005 (UTC)
It is often required that row header cells are not centered. With the old template:prettytable this worked by adding align="left". However, with the class "wikitable" this does not seem to work anymore. Adding style="text-align: left" still works. See examples here:
appearance rowheader | extra formatting in rowheader | comment |
---|---|---|
r1 | none | header centered as per style |
r2 | align="left" | straight override not working |
r3 | style="text-align: left" | style override working |
A few articles currently suffer from this effect. Can someone explain why straight alignment does not override the stylesheet? Is it conforming css specs? − Woodstone 21:43, 25 September 2005 (UTC)
th
s, i.e. something like.wikitable th:first-child {text-align: left;} .wikitable tr:first-child th {text-align: center;}
>
) to result in fewer false positives (possible with nested tables), but would probably work in fewer browsers, esp. Internet Explorer. (IIRC IE6 supports :first-child
, otherwise the point is moot.)Since a few weeks the class "wikitable" has been in use to implement the various templates {{ prettytable}}. It seems to be working fine. However during experimentation phase a class "prettytable" was added to the Common.css stylesheet as well. Now the time has come to eliminate one of the names.
− Woodstone 10:09, 5 October 2005 (UTC)
This page is now imported directly into the HTML for all skins. The @import lines can be removed from all the skin-specific CSS pages, after a few days have elapsed for cache expiry. -- Tim Starling 10:55, 23 October 2005 (UTC)
I'm shortly going to add a little bit of CSS to this file for the proposed new Main Page design. This is for testing purposes only, to check if this design works correctly live on Wikipedia. It will not alter the display of the live site. Please don't remove it for the moment. Thanks, Tom- 23:19, 25 October 2005 (UTC)
The hardcoded css for monobook at http://en.wikipedia.org/skins-1.5/monobook/main.css includes the lines:
img { border: none; vertical-align: middle; }
Classic, Nostalgia, Cologne Blue, and I suspect most of the new skins do not, and where this is not taken into account, the results look horrible. (See, for example, Template:Mac-stub, where the once-standard table code still visible in Template:Metapicstub was recently removed.) Rather than quixotically searching through the template namespace and adding tables to control this visual issue (usually a poor idea), with confused monobook users following me and breaking them again, can this be added here? — Cryptic (talk) 06:30, 28 October 2005 (UTC)
div#bodyContent img { border: none; vertical-align: middle; }
Hi guys, I have my own website running on the wiki software and I am beating my brain trying to figure out how to get rid of the external link arrow on my reference template. I've got what seems to be all the pieces needed in the default skin's Summabook.css file, as well as monobook's Monobook.css. And for good measure, it's in Common.css (even though I don't import it into the other .css files like wikipedia does) and the main.css file for the skin. How can it not be loading the code and getting rid of the arrows? What's missing? David Bergan 07:18, 1 November 2005 (UTC)
#bodyContent a[href^=http://], #bodyContent a[href^=gopher://] {background-image:url(external.png)}
Would anyone object to removing text-align: justify
from .notice and .messagebox? This serves no purpose, except to add big ugly gaps between the words and make it looks like it belongs to some other web site. —
Michael
Z. 2005-11-15 19:30 Z
I originally reported this here, not knowing where else to post it. I filed a bug and was referred here, so here's the original message, somewhat redacted:
There are two problems with the Common stylesheet that should be fixed ASAP. First, the filter statement on line 225 should simply be removed: It is nonstandard and produces errors messages in Firefox's debugging console. Secondly, the line-height property on line 208 has no units (should be 1.5em, I'm sure), which is invalid and also causes error messages. — HorsePunchKid→ 龜 19:36, 18 November 2005 (UTC)
y with macron, ȳ, Unicode 233 hex, which is used in Old English morphology, appears as a box on my computer even though it is enclosed in Template Unicode. The same problem occurs with Template IPA: ȳ
I use MSIE 6.0, and my fonts include Arial Unicode MS, Microsoft Sans Serif.
The problem appears to be that Arial Unicode MS appears before Microsoft Sans Serif in MediaWiki:Common.css, but Arial Unicode MS doesn't support codes 218-24F. I propose that the order of these two fonts be reversed. -- teb728 01:31, 3 December 2005 (UTC)
The contrast in wikitable is unnecessarily low. Can we increase it please? Bobblewik 12:33, 14 November 2005 (UTC)
T-34 Model 1940 | T-34 Model 1941 | T-34 Model 1942 | T-34 Model 1943 | T-34-85 | T-44 | |
---|---|---|---|---|---|---|
Weight | 26 t | 26.5 t | 28.5 t | 30.9 t | 32 t | 31.9 t |
Gun | 76.2mm L-11 | 76.2mm F-34 | 76.2mm F-34 | 76.2mm F-34 | 85mm ZiS-S-53 | 85mm ZiS-S-53 |
Ammunition | 76 rounds | 77 rounds | 77 rounds | 100 rounds | 60 rounds | 58 rounds |
Fuel | 460 L | 460 L | 610 L | 790 L | 810 L | 642 L |
Road range | 300 km | 400 km | 400 km | 465 km | 360 km | 300 km |
Armour | 15–45 mm | 20–52 mm | 20–65 mm | 20–70 mm | 20–90 mm | 15–120 mm |
Cost | 270,000 rubles | 193,000 rubles | 135,000 rubles | 164,000 rubles |
[removed wikitable version with right-aligned numbers; the version below is better —
Michael
Z. 2005-12-7 21:45 Z]
I definitely find the second one easier to read. But you misunderstood one thing I said. Centering is disadvised when "no horizontal rules" are present. Since wikitable has rules (and within the columns dimensions are unequal) the numbers could have stayed centered. My preference would be like below. (Note that the original smaller characters also reduced legibility.) − Woodstone 21:28, 7 December 2005 (UTC)
T-34 Model 1940 |
T-34 Model 1941 |
T-34 Model 1942 |
T-34 Model 1943 |
T-34-85 | T-44 | |
---|---|---|---|---|---|---|
Weight (tonnes) | 26 | 26.5 | 28.5 | 30.9 | 32 | 31.9 |
Gun | 76.2mm L-11 | 76.2mm F-34 | 76.2mm F-34 | 76.2mm F-34 | 85mm ZiS-S-53 | 85mm ZiS-S-53 |
Ammunition (rounds) | 76 | 77 | 77 | 100 | 60 | 58 |
Fuel (litres) | 460 | 460 | 610 | 790 | 810 | 642 |
Road range (km) | 300 | 400 | 400 | 465 | 360 | 300 |
Armour (mm) | 15–45 | 20–52 | 20–65 | 20–70 | 20–90 | 15–120 |
Cost (rubles) | 270,000 | 193,000 | 135,000 | 164,000 |
It ain't working! When I print, it expands the external URLs. This is having a major effect in a few template:
Can someone fix this? - Ta bu shi da yu 08:08, 5 December 2005 (UTC)
Since a large portion of people are color blind in some sense, we should address this quickly:
(copied from User talk:Jimbo Wales)
— BRIAN 0918 • 2005-12-8 00:04
Please change .infobox.sisterproject to be "width: 20em", which matches more closely how these were originally (which was 250px, but em is better). -- Netoholic @ 14:23, 15 December 2005 (UTC)
Seeing the edit http://en.wikipedia.org/?title=List_of_The_Simpsons_episodes&diff=31567503&oldid=31556419 – where a hard-coded color is applied to every 2nd table row – earlier today made me think: "we need a standard color for highlighting stuff/text/table rows". How about adding
table.wikitable .highlight, table.prettytable .highlight { background: #ececf6; }
to this CSS. Then we might simply use
{| class="wikitable" |- | one row || one row |- class="highlight" | another || another row |}
instead of the hardcoded colors? -- Fred Bradstadt 08:39, 16 December 2005 (UTC)