MediaWiki talk:Monobook.css/Archive 4

message: Is this the place to point out that the "My contributions" link doesn't go bold when you're on that page? Stevage 12:38, 15 May 2006 (UTC)
replies: text: Woa, I never noticed that before. It would be nice if the link would be bolded while I'm looking at the page, more for aesthetic reasons than for practical ones. Can someone make it happen? AmiDaniel (talk) 07:04, 24 May 2006 (UTC)
replies: text: This is a php problem, not a CSS problem.  Try bugzilla.  Dragons flight 07:13, 24 May 2006 (UTC)
replies: text: This issue has already been reported. — Edward Z. Yang(Talk) 23:33, 11 June 2006 (UTC)
replies: text: I just noticed it and I was going to report it on the page. I also noticed the log out link doesn't get bold when clicked. Wait a minute... crap... --SUBZ3R0 ( Talk | E-mail ) 06:15, 1 April 2007 (UTC)
thread_title: My contributions

message: On the Template_talk:Dynamic_navigation_box_with_image#Image_broken page there was an issue where NavHead was being displayed over NavPic. This is due to the 'position: relative' line in the class definition. That line doesn't appear in the original German and other language versions of this class. Do we know what it is being used for? I was able to get around the issue on that template by adding a 'position: relative' style to the NavPic section and settign it to a higher z-index than NavHead, but is this something we should change in the class rather than on individual templates? --CBD 12:43, 22 June 2006 (UTC)
thread_title:  NavHead 

message: I suggest adding the line
 table { background-color: transparent; }
Currently, the default background color is white, which doesn't make a lot of sense and looks bad outside of article space.  See Special:Movepage/Rabbit (or any Special:Movepage) for an example.
This has been discussed on the village pump here.  A suggestion was made to create a new CSS class, but first of all that should be unnecessary and second of all you may as well use inline style if you're going to do that. —Simetrical (talk • contribs) 22:56, 9 July 2006 (UTC)
replies: text: Never mind, someone (Tim Starling) finally fixed the default. —Simetrical (talk • contribs) 04:48, 21 July 2006 (UTC)
thread_title:  Set table background to transparent by default 

message: My nav menu has just become messed up. Using IE7 Beta 2, the clipping between the links of the nav menu has increased to the approximation of double-spaced. Does anyone have any thoughts about this (other than use a different browser...yeah, I tried it in FF both logged out and in--haven't tried it logged out in IE yet--and it was fine). Any thoughts? -Mysekurity 23:49, 14 August 2006 (UTC)
replies: text: Nope, tried it logged out. Colors are usual anon's, but the spacing is still ginormous. Clearing cache didn't work either. I imagine it had something to do with Timwi's change, but I'm not sure.. Any help would be appreciated. -Mysekurity 23:51, 14 August 2006 (UTC)
replies: text: Looks fine for me in IE6; I don't see anything in Timwi's change that could have done anything.  Weird. —Mets501 (talk) 01:01, 15 August 2006 (UTC)
replies: text: Um, whups. I guess that's why it's a beta. After a restart, the nav links look fine. Thanks... -Mysekurity 01:42, 15 August 2006 (UTC)
replies: text: It looks really good. Good work guys! --Siva1979Talk to me 03:33, 15 August 2006 (UTC)
thread_title:  Navigational Clipping 

message: Fix for Preferences (Time tab skrew up in Firefox)
.prefsectiontip {
  float: left;
  width: 98%
}
--82.200.186.14 07:24, 28 August 2006 (UTC)
thread_title:  Fix for Preferences 

message: Why are NavFrame and NavHead here rather than in common.css?  Because of this template:Navigation worked only in monobook skin.  As a temporary expediency I've inlined these styles in this template, but it seems to me moving these styles to common.css would be a better fix.  Is there some reason not to do this? -- Rick Block (talk) 13:24, 24 November 2006 (UTC)
thread_title:  NavFrame and NavHead 

message: I would like to change 
td.diff-addedline, td.diff-deletedline, td.diff-context {
    font-size: 85%;
    color: inherit;
}
to
td.diff-addedline, td.diff-deletedline, td.diff-context {
    vertical-align: top;
    font-size: 85%;
    color: inherit;
}
so the text align better. →AzaToth 18:27, 5 December 2006 (UTC)
replies: text: Done —Mets501 (talk) 15:38, 10 December 2006 (UTC)
thread_title:  diff align 

message: Shouldn't this be at the common CSS file, not here? Karl Dickman talk 11:24, 12 December 2006 (UTC)
replies: text: It doesn't show for logged-in users, and anons can't change their skin. --ais523 11:10, 13 December 2006 (UTC)
thread_title:  Fundraising notice 

message: What is people's opinion on the addition of
  .mw-plusminus-pos {
      color:green;
      font-weight:bold;
  }
  .mw-plusminus-neg {
      color:red;
      font-weight:bold;
  }
to the css?
It would make a recent change like this:
23:55 Danny Dyer (cur; last) . . (+4,033) . . AntiVandalBot (Talk | contribs) (BOT - rv 80.176.133.116 (talk) to last version by Ashworth66)
look like this:
23:55 Danny Dyer (cur; last) . . (+4,033) . . AntiVandalBot (Talk | contribs) (BOT - rv 80.176.133.116 (talk) to last version by Ashworth66)
and
23:55 Danny Dyer (cur; last) . . (-4,033) . . AntiVandalBot (Talk | contribs) (BOT - rv 80.176.133.116 (talk) to last version by Ashworth66)
look like this:
23:55 Danny Dyer (cur; last) . . (-4,033) . . AntiVandalBot (Talk | contribs) (BOT - rv 80.176.133.116 (talk) to last version by Ashworth66)
—Mets501 (talk) 00:19, 22 December 2006 (UTC)
replies: text: I have copied this css ruleset to common.css, and will remove it from monobook provided that there are no objections.  Karl Dickman talk 23:43, 24 December 2006 (UTC)
thread_title:  Words added/removed 

message: According to the W3C CSS Validator, these are not valid CSS colors. I suggest we replace darkgreen with #006400 and darkred with #8B0000 per , this should let the page pass the validator. HighInBC (Need help? Ask me) 01:03, 10 February 2007 (UTC)
replies: text: Ok, I changed it, now the validator says "Congratulations! No Error Found.". HighInBC (Need help? Ask me) 13:49, 17 February 2007 (UTC)
replies: text:  The proper css color names, incidentally, are green and maroon --Random832 14:09, 4 April 2007 (UTC)

text: Ahh, neat. HighInBC(Need help? Ask me) 14:11, 4 April 2007 (UTC)
thread_title:  darkgreen and darkred 

message: Hi, The default CSS for the HTML-rendered math are breakable (as opposed to using non-breaking spaces). This isn't desirable, since parts of a single equation can appear on more than one line. To fix this, you can edit your Special:Mypage/monobook.css to:
span.texhtml {
        white-space: nowrap;
        font-family: serif;
}
This idea was hinted to me here. I proposed this at the Village pump for the default monobook.css, but not a single comment was posted in reply, and was promptly archived within a week. I don't think it's a poor idea, nor is it controversial at all, so I thought I would add it here to collect more dust. +mwtoews 08:37, 17 February 2007 (UTC)
replies: text: This isn't the default behavior for inline LaTeX, at least.  Long equations may need to be broken up. —Simetrical (talk • contribs) 19:47, 23 March 2007 (UTC)
thread_title:  Suggestion for default monobook.css for nowrap span.texhtml 

message: This applies to readers who are not logged in.  The "Your continued donations keep Wikipedia running!" text blurb in the top right corner of the page is not pushed in far enough to the left.  If a user is reading an article which is both featured and spoken, for example DNA, then the spoken article icon overlaps the "g!" of the donation text.  I'd suggest either moving the text inwards, or stacking the icons on top of one another. Phuzion 21:02, 24 February 2007 (UTC)
thread_title:  Overlapping text/images 

message: Removal of the "cite this page" link from the Main Page has just come up on Talk:Main Page and I seem to remember it coming up before (either there or elsewhere). Adding body.page-Main_Page #t-cite to the list of things not to display on the Main Page (right at the top) would presumably do this? – Qxz 06:20, 23 March 2007 (UTC)
replies: text: Last time it was during the Main Page namespace discussion (in which you participated, if I remember rightly); it was mentioned that the Main Page's cite link was a result of the namespace it was in. --ais523 18:11, 23 March 2007 (UTC)
thread_title:  Not citing the Main Page 

message: Why is "cite this article" in the sidebar toolbox on the main page? It just seems embarrassing, especially after all the effort that has clearly gone into making the page near-perfect. Sitewide CSS should remove it, if this line is added to this page:
 .page-Main_Page #t-cite {display: none}
— Jack · talk · 06:23, Friday, 23 March 2007
Done. —Ruud 09:52, 23 March 2007 (UTC)
thread_title:  "cite this article" on the main page 

message: Is there a "wiki" method to mark-up horizontal lists, like that at http://en.wikipedia.org/wiki/A34_road#Former_route, so that they're rendered as an HTML list, styled horizontally? Elsewhere, (for example http://www.westmidlandbirdclub.com/test/) I use something like:

.horizontal
		{
	  	padding: 0;
		margin-top: 0;
		margin-left: -1.5em;
		margin-bottom: 0.5em;
		margin-right: 0;
		}
.horizontal li 
		{ 
	  	display: inline;
		font-size: 90%;
		line-height: 1.5;
		border-left: 0.1ex solid;
		padding-left: 0.5em;
		padding-right: 0.5em;
		}
.horizontal li:first-child
		{
		border-left: none;
		padding-left: 0;
		}

but I have no idea how to apply that to a list, or to a template for a list, in WikiCode. The border-left separator could, of course, be omitted if so desired. 
Ideally, the solution would take the form:

  {{starthorizontallist}}
  *cat
  *dog
  ...
  *horse
  {{endhorizontallist}}  (if required)

Andy Mabbett 19:08, 29 March 2007 (UTC)
replies: text: Very easy to do. Just add that code to the sitewide css and then add  before the list and  after the list in the article. —METS501 (talk) 22:20, 29 March 2007 (UTC)
replies: text: "Just add that code to the css"  - where? And is it wise (or acceptable) to expect users to insert DIVs? How do we then let people know that that option is availabale to them? Andy Mabbett 22:34, 29 March 2007 (UTC)
replies: text: I was speaking purely from a technical standpoint.  Putting the divs in a template works just as well.  The css can be added anywhere in the sitewide css at MediaWiki:Common.css. —METS501 (talk) 22:44, 29 March 2007 (UTC)
replies: text: Common.css seems to be protected. Andy Mabbett 22:54, 29 March 2007 (UTC)
replies: text: Yes, and there needs to be community acceptance before the code is added.  I suggest suggesting this change at MediaWiki talk:Common.css and possibly WP:VPR. —METS501 (talk) 23:08, 29 March 2007 (UTC)
replies: text:  Thank you. I'd already flagged up this discussion at the former; and have now done so at the latter. Andy Mabbett 23:13, 29 March 2007 (UTC)
replies: text:  Great! —METS501 (talk) 00:19, 30 March 2007 (UTC)
thread_title:  Horizontal lists 

message: I propose we centre images on the image page. —Ruud 15:24, 1 April 2007 (UTC)
replies: text: I think it looks much better on the left. Images that are taller than wide tend to have too much white space on each side otherwise. HighInBC(Need help? Ask me) 15:26, 1 April 2007 (UTC)
replies: text: I agree. It's better on the left. —METS501 (talk) 15:28, 1 April 2007 (UTC)

text: Yes, but images like this: :Image:Totem Park pole 2.jpg, look just terrible(a matter of aesthetics and personal preference of course) if centered. HighInBC(Need help? Ask me) 15:51, 1 April 2007 (UTC)
replies: text:  Only few images have such extreme propotions. —Ruud 17:05, 1 April 2007 (UTC)

text: Thousands and thousands of images will have that problem. HighInBC(Need help? Ask me) 17:51, 1 April 2007 (UTC)

text: And you might not even think to look in the middle to see a tiny image like :Image:X mark 18x18 04.gif. —METS501 (talk) 19:42, 1 April 2007 (UTC)

text: Those do look pretty bad. HighInBC(Need help? Ask me) 19:50, 1 April 2007 (UTC)
replies: text:  That's your opinion. —Ruud 20:24, 1 April 2007 (UTC)

text: How about, small images are hard to find because they are floating off in nowhere land? HighInBC(Need help? Ask me) 20:38, 1 April 2007 (UTC)
replies: text:  The images used in articles are usually at least 180px wide; smaller images will still be right at the top. —Ruud 20:49, 1 April 2007 (UTC)
thread_title:  Centering images on image pages 

message: Something I run into every so often is trying to locate what has been removed or added in a page change when it is just a period, comma, dash or other very small single character. For instance, take a look at the top changed section in this diff.  It takes a little while to realize someone removed the minus sign on the record low temperature.  I am suggesting a change in this CSS to add the following two lines to the .diffchange {} CSS selector:
 background-color: #FF9999;
 color: #000000;
I have implemented it on my own monobook.css and it seems to make the above minus sign *much* easier to spot in the diff. --MattWright (talk) 00:15, 4 April 2007 (UTC)
replies: text: I like this idea, and I just experimented with some different colors.  In my opinion, the best combination that I came across was white text on a dark blue background (the same shade used for our links, so it matches nicely).
 .diffchange { background-color: #002bb8; color: #fff; }
—David Levy 01:12, 4 April 2007 (UTC)

text: MattWright, I don't think you will be able to find consensus on which exactly style to use. And even if you do, after this is implemented a lot of people will come to forums asking to revert. In any case, you're welcome to add your suggestion at WikiProject_CSS. P.S. for me the following is good enough. — Alex Smotrov 22:08, 10 April 2007 (UTC)
replies: text: I am sorry, but this diff states how I feel about this proposed alteration. However the idea has merit different colors, let me try ".diffchange {border: 1px dotted gray}". HighInBC(Need help? Ask me) 22:14, 10 April 2007 (UTC)

text: I really like ".diffchange {border: 1px dotted gray}", it helps find stuff but is not distracting or ugly. HighInBC(Need help? Ask me) 22:16, 10 April 2007 (UTC)

text: May I suggest: ".diffchange {padding: 0px 2px 0px 2px; border: 1px dashed black;}", it is what I have settled on. HighInBC(Need help? Ask me) 22:32, 10 April 2007 (UTC)
replies: text: I find that still makes me hunt a little for some really minor edits, but it is better than the existing CSS.  I understand consensus on a CSS change is hard, but this functionally improves the site. Before I realized I could change the CSS in this way, I have dismissed some edits that I just couldn't figure out what was changed without a lot of work. I feel that for the casual user who doesn't understand this, they could be passing up on reverts of bad edits such as the one linked above where a serious change was introduced in the article, but it was really hard to tell. --MattWright (talk) 22:42, 10 April 2007 (UTC)

text: With the one I suggested, that diff stands out very well, the pixel size could be increased to 2, but it may be overkill. HighInBC(Need help? Ask me) 22:44, 10 April 2007 (UTC)

text: That stands out, making the dots red. HighInBC(Need help? Ask me) 22:46, 10 April 2007 (UTC)
replies: text: I love the red dashes!  They draw attention to the subtle changes without uglifying the text.  —David Levy 22:56, 10 April 2007 (UTC)

text: Adding a margin to the right of 1px stops the box from touching the character to the right of it, see  before and after. HighInBC(Need help? Ask me) 23:17, 10 April 2007 (UTC)
replies: text: Looks nice. --MattWright (talk) 23:58, 10 April 2007 (UTC)
replies: text: Hm. I tend to be partial to dotted, rather than dashed, lines. It could just be a personal aesthetic thing, though. GracenotesT § 20:17, 11 April 2007 (UTC)

text: This is a fantastic idea. --- RockMFR 14:59, 13 April 2007 (UTC)
thread_title:  Better rendering for .diffchange in diff's... 

message: Compare history page of Main Page with eg. history page of "Wikipedia" article. There is a difference on top - in case of Main Page there is no (among other things) link "View logs for this page". I guess this line:
body.page-Main_Page #contentSub,
is responsible... What is the reason for this? Thanks. Gen. von Klinkerhoffen 23:00, 1 May 2007 (UTC)
replies: text: It's to hide the title ("Main Page") from the actual main page.  The workaround (as far as I know) would be using javascript, but I don't think that's really necessary. —METS501 (talk) 23:19, 1 May 2007 (UTC)
replies: text: Actually, the title is hidden with h1.firstHeading. The contentSub doesn't seem to have anything inside it on article pages, so I too have no idea why it's hidden on the Main Page. P.S. It was Javascript (to hide stuff on Main Page) until a couple of months ago when MediaWiki introduced additional classes for <body> tag. — Alex Smotrov 00:04, 2 May 2007 (UTC)
replies: text: I've made a patch that will include a class based on the action parameter, e.g. action-history, action-view (the default). Hopefully it gets accepted. Update: looks like there was already another one. Mike Dillon 00:12, 2 May 2007 (UTC)
replies: text: The content-sub hiding on the Main Page is to get rid of the 'Redirected from' notice on redirects like Main page. --ais523 16:37, 2 May 2007 (UTC)
thread_title:  Why some stuff is hidden on Main Page? 

message: Sorry, I meant to put this on MediaWiki talk:Common.css. I'm moving it now. --ais523 16:14, 17 May 2007 (UTC)
thread_title:  Listifying special page transclusions 

message: Is this the script that set's the flowery background behind everything? I was thinking about using it on my Wikia, can I? --Steinninn talk 01:10, 1 June 2007 (UTC)
replies: text: The flowery image behind everything is an open book, and is set in main.css, which comes with every installation of MediaWiki since 1.5.  It will appear in the Monobook skin by default on your Wikia if you have not modified the skin. —Simetrical (talk • contribs) 21:41, 1 June 2007 (UTC)
thread_title:  Background image 

message: Could somebody possibley add
 /* rounded corners - Mozilla/Firefox only */
 .pBody
 {
     padding: 0.1em 0.1em;
     -moz-border-radius-topright: 0.5em;
     -moz-border-radius-bottomright: 0.5em;
 }
 
 #p-cactions ul li, #p-cactions ul li a
 {  
     -moz-border-radius-topright: 0.5em;
     -moz-border-radius-topleft: 0.5em;
 }
 
 #content, .toc
 {
     -moz-border-radius-topleft: 0.5em;
     -moz-border-radius-topright: 0.5em;
     -moz-border-radius-bottomleft: 0.5em;
     -moz-border-radius-bottomright: 0.5em;
 }
for rounded corners on some infoboxes? 77.99.107.117 22:02, 3 July 2007 (UTC)
replies: text: I strongly oppose this addition!  This is an experimental, Gecko-specific feature, and an UGLY one at that.  It has no place in the site-wide CSS.  —David Levy 22:08, 3 July 2007 (UTC)
thread_title:  Rounded corners on interface elements 

message: I would like to suggest to add the following code:
 div.thumb {
        border: none;
 }
 div.tright {
        border: none;
        margin: 0.5em 0 0.8em 1.4em;
 }
 div.tleft {
        border: none;
        margin: 0.5em 1.4em 0.8em 0;
 }
... to get this instead of this effect (the difference is the ugly white border around the thumb). The code is copied from the German wikipedia. Freestyle 13:02, 4 August 2007 (UTC)
replies: text: Melsaran (formerly Salaskаn) 14:36, 4 August 2007 (UTC)

text: Seems uncontroversial.  Done. Cheers. --MZMcBride 14:39, 4 August 2007 (UTC)
replies: text: Thank you and Melsaran too for the support vote :) .Freestyle 15:15, 4 August 2007 (UTC)
thread_title:  CSS code to remove ugly border around thumb images 

message: Can we please clean up this CSS page? Please remove the following ∴ Alex Smotrov 19:09, 4 October 2007 (UTC)
replies: text: I completely agree that this CSS needs updating, however, the changes need to be made carefully. Things should only be removed if we know they're no longer needed (e.g., #mytabs) and we're sure that they won't be needed in the future (e.g., #siteSub a). I suggest creating a temporary subpage where the changes can be made and everything can be adjusted and then the CSS can be updated all at once. That way, we'll hopefully avoid the majority of caching issues. Cheers. --MZMcBride 20:04, 4 October 2007 (UTC)
replies: text: Unfortunately I don't see much activity discussing this. Would it help if I created the userscript that disables Monobook.css, imports "New Monobook.css" and provides a tab on the top to quickly switch between them? Then some test users could walk Wikipedia pages for a day or two and confirm that nothing is broken ∴ Alex Smotrov 14:39, 5 October 2007 (UTC)
replies: text: Yeah, that's an option. It's only been a day since you posted to this talk page, so I'm not concerned people haven't responded yet. I'm going to cross-post to MediaWiki talk:Common.css and WP:VP/T and try to get more input. Personally, I think having a /temp page at MediaWiki:Monobook.css/temp may be the best option. Let's see what others think. --MZMcBride 02:47, 6 October 2007 (UTC)
replies: text:  I'm not sure whether the comments should be removed. I mean, not everyone reads the talk page... Titoxd(?!? - cool stuff) 06:04, 7 October 2007 (UTC)
replies: text: I think the comments should be kept to a minimum. Long explanations/instructions should be on a separate documentation page ∴ AlexSm 17:59, 17 October 2007 (UTC)

text: I started editing "my version", then realized that I'm making too many changes and nobody will accept them in this form anyway. Besides, any change has to be discussed anyway, why not discuss it first? ∴ AlexSm 17:59, 17 October 2007 (UTC)
thread_title: Cleanup

message: More than half of the current Monobook.css either should be removed or moved into Common.css. It's so easy to thoughtlessly add new rules into these files, but not so easy to clean up the mess afterwards. I'm in the process of editing global CSS/JS files in the project where I have an admin flag and. I thought I could also help English Wikipedia a little. If I'm the only one interested in improving these files here, then I can as well stop trying. I'm making one last attempt, and this time I tried to explain things a bit better. All the following rules can be removed ∴ AlexSm 17:59, 17 October 2007 (UTC)
replies: text: Done. Thank you for simplifying this. Cheers. --MZMcBride 05:17, 18 October 2007 (UTC)
replies: text: Thank you ∴ AlexSm 16:19, 18 October 2007 (UTC)
thread_title: Cleanup (again)

message: Please remove the following:
#p-nav h5 {
   display: none;
}
 
#p-nav .pBody {
   padding-right: 0;
}
 
#p-nav a {
   display: block;
   width: 100%;
}
added (plus next diff) in January 2005.  Unfortunately MediaWiki:Sidebar's history doesn't go that far, and that user is inactive now. However it's clear from the edit summary that the intent was to remove the header «navigation» from the portlet on the left, and that portlet id was p-nav (now it's p-navigation).
/* try adding here, this had no effect in MediaWiki:Common.css */
.plainlinksneverexpand a.external.text:after {
 display: none !important
}
added in September 2005, duplicates exactly same rule in MediaWiki:Common.css
/* Remove padding from external links displayed without icon */
#bodyContent .plainlinks a {padding: 0 !important}
added in March 2005, duplicates this rule in main.css :
#bodyContent .plainlinks a {
	background: none !important;
	padding: 0 !important;
}
∴ AlexSm 16:19, 18 October 2007 (UTC)
replies: text: Do you have access to the MediaWiki code to verify whether or not there are any conditions under which these CSS rules will appear? (This question may be irrelevant, but it's just a possible concern) -- Renesis (talk) 21:27, 18 October 2007 (UTC)
replies: text: MediaWiki code is irrelevant here; CSS only tells the browser how to display all elements. See Wikipedia:Catalogue_of_CSS_classes for a list of currently implemented CSS classes and the files they are stored in.  — Edokter • Talk •  21:32, 18 October 2007 (UTC)

text: PS. The cleanup has some side-effects, see Wikipedia:Village pump (technical)/Archive 141#Underlined links.  — Edokter • Talk •  21:42, 18 October 2007 (UTC)
replies: text: I already replied there 2 hours ago ∴ AlexSm 22:06, 18 October 2007 (UTC)
replies: text:  Done. Cheers. --MZMcBride 20:58, 19 October 2007 (UTC)
thread_title:  Cleanup (part3) 

message: See this discussion on the administrators' noticeboard: it seems the hiding of the #contentSub section on the main page makes it confusing if someone creates a redirect to Main Page.  Since the section is normally empty, I see no actual need to hide it.  I'd therefore like to propose that the line that reads "body.page-Main_Page #contentSub," be removed from this stylesheet.  Any objections?  —Ilmari Karonen (talk) 16:19, 26 October 2007 (UTC)
replies: text: Since no-one has objected, and since my testing didn't show any obvious breakage, I've made the change.  —Ilmari Karonen (talk) 18:26, 5 November 2007 (UTC)
thread_title:  Not hiding #contentSub on the Main Page 

message: I recently copied a few hundred fonts from an old XP installation to my current reformat, and my mediawiki pages started to look off in Interenet Explorer. I tried to check monobook.css to see if I'd installed some font that's higher in the font family heierarchy, but I don't see a font family in the monobook.cs. Does anyone know what is wrong, or where the font family is? This wasn't a problem on the old Xp install though, so I'm baffled. 
Here is an image of the issue; Firefox shows how it used to look in IE and still looks in Fox TheHYPO 09:45, 3 December 2007 (UTC)
replies: text: There is no specific font set, just a font-family. On wikipeida that is "sans-serif". On Windows and Internet Explorer, that usually results in Arial being used, or otherwise the first sans-serif in the fontlist. In Firefox, one can set the font for sans-serif explicitly.  — Edokter • Talk •  10:28, 3 December 2007 (UTC)
replies: text: For anyone having trouble finding this, it's hard-coded in the main.css file mentioned above.  See http://en.wikipedia.org/style/monobook/main.css where body is defined as "x-small sans-serif;" Of course, anyone can override this (or anything else) in their Special:Mypage/monobook.css if they see fit. Superm401 - Talk 02:54, 23 December 2007 (UTC)
thread_title: Fonts