MediaWiki talk:Monobook.css/Archive 2

message: Would someone please add this to the file:
     #bodyContent .plainlinks a {padding: 0 !important}
Thanks. – ABCD 03:20, 24 Feb 2005 (UTC)
replies: text: Another, probably better way would be to add the !important code to the http://en.wikipedia.org/style/monobook/main.css file. – ABCD 03:59, 24 Feb 2005 (UTC)
replies: text:  This was reported twice but ignored. Goplat 04:32, 24 Feb 2005 (UTC)
replies: text: Now added to Monobook.css, at least, and seems to be working.  Should it be added to other skin stylesheets as well?  (And if so, what are their names?  I couldn't find a list.... — Catherine\talk 19:37, 10 Mar 2005 (UTC)
thread_title:  class="plainlinks" fix 

message: Village pump (technical)#section edit links showing up badly - this may be a problem with the CSS, or it may be a Mozilla/Firefox/etc problem that can still be fixed by changing the CSS. Please have a look. --SPUI (talk) 17:55, 1 Mar 2005 (UTC)
thread_title:  messed up section edit links - CSS or Mozilla issue? 

message: I have a query at Wikipedia_talk:A_proposal_re_BCE-CE_Debate#Let's implement a preference-based solution today about what is technically possible with CSS. If answered positively, it may help break the deadlock in the interminable BC/BCE debate, so please have a brainstorm about the best solution and comment there! Many thanks. Pcb21| Pete 10:11, 16 May 2005 (UTC)
thread_title:  A request for CSS experts 

message: I have added a new class "plainlinksneverexpand" that behaves like the existing class "plainlinks", but not only suppresses the external link arrow but also URL expansion. Resulted from this discussion at the Village pump. See also Template talk:Ref and Template:Ref, where this is used. Does this need to be ported over to other skins (Cologne, Classic)? Lupo 20:36, 24 May 2005 (UTC)
replies: text: Does this also fix the Template_talk:Ref#Printing_problem., where URLs of references were being printed? (Not necessary because the references are further down in the article) (SEWilco 06:41, 26 May 2005 (UTC)
replies: text: Yes it does. In fact, that was what prompted me to add this new class. Lupo 07:47, 26 May 2005 (UTC)

text: Is it possible that recent edits to monobook.css,  or  broke the working of footnotes? This was pointed out by Raul654 at Wikipedia talk:Featured article candidates#Extremely important problem!. I've crossposted this at the two relevant talk pages as I don't know where to search for the problem. — mark ✎ 17:39, 4 Jun 2005 (UTC)
replies: text:  The date given there is June 2.  The  and  behavior has been discussed since June 1. Wikipedia_talk:Footnote3#template:note_now_broken (SEWilco 03:37, 5 Jun 2005 (UTC)
replies: text: Can't June 2 equal June 1 depending on the relative timezones? Now if you can find a complaint before June 1, or show the time of the problem is before the time of the fix, things would become more interesting. --cesarb 20:24, 11 Jun 2005 (UTC)
thread_title:  New class "plainlinksneverexpand" 

message: I noticed it's common for the different skins to get out of sync (things that should be added to all of them are only added to Monobook.css, until someone else takes notice and updates the others). What would you think about creating a MediaWiki:Common.css and adding the following line to the top of all the skin stylesheets:
@import "/w/index.php?title=MediaWiki:Common.css&action=raw&ctype=text/css&smaxage=2678400";
This way, content styles (like for instance .notice) could be updated in a single location, and the skin-specific stylesheets would need to worry only about the user interface. Since it would be added to the top, the CSS cascade could be used to override the common style, if needed.
--cesarb 9 July 2005 19:16 (UTC)
:Since nobody objected, being bold and creating. --cesarb 16:34, 11 July 2005 (UTC)
replies: text: I have moved all the CSS which was common for the 4 skins I could find (where's MySkin's CSS?) to MediaWiki:Common.css. Now the CSS for the other three skins is empty except for the import of Common.css. I believe there's more to move there (and in fact I moved one of them, #disambig); the other skins seem to have been neglected for a long time. I have checked it all validates and works on Firefox, but I haven't tested on IE. --cesarb 17:18, 11 July 2005 (UTC)
replies: text: Myskin doesn't have CSS.  That's the whole point of it.  You supply your own.  You can user myskin to make custom skins. BLANKFAZE | (что??) 17:51, 21 July 2005 (UTC)
thread_title:  Common CSS 

message: The "new" look is stupid. Please change it back. - Ta bu shi da yu 09:29, 13 July 2005 (UTC)
replies: text: Did someone change them again? Suddenly I get red question marks, instead of red text/underlines. -- nae'blis (talk) 19:18, 21 July 2006 (UTC)
thread_title:  What the heck happened to redlinks?! 

message: Can somebody revert the spoken code to:
 #spoken {
  display: block !important;
  border-bottom-style: none;
  float: right;
  position: absolute;
  right: 2%;
  top: 0.6em;
 }
The current code doesn't work.  Joe D (t) 13:50, 20 July 2005 (UTC)
thread_title:  Spoken 

message: See the edit links on . - Omegatron 19:54, July 29, 2005 (UTC)
:I presume (although the diff links have gone now that the page is no longer current) that you are referring to an edit link gone south.  This is a common and probably unfixable fault with floating objects in CSS. smoddy 22:16, 29 July 2005 (UTC)
replies: text:  Bugzilla:4855 is related, though not a solution. — Omegatron 04:40, 8 February 2006 (UTC)
thread_title:  Possible CSS problem with floating images 

message: Should the background color of the new Portal namespace be the same light blue it currently is, or should it be changed to white (same as the articles and the Main Page)? Now that it's a separate namespace, it would be very easy to change the color, and it would better match the look of the Main Page. --cesarb 18:02, 28 August 2005 (UTC)
thread_title:  Portal namespace 

message: This is a proposal to address the difficulties many users experience when they try to thematically navigate Wikipedia after they leave the Main Page: add one (or add one and expand one) topical navigation menu to Mediawiki:Monobook.css.  The elements would be those contained in Template:Categorybrowsebar located on the Main Page.  In this template, the first line focuses on the main categories while the second line focuses on browse options. Adding the elements to this style sheet would allow Wikipedia to have a topical, top-level navigation scheme, based on the primary categorization scheme, that would help users move about logically and quickly from any page.  Another benefit of this implementation would be that Template:Categorybrowsebar could be removed from a prominent position on the Main Page and several other high-level pages.  — RDF talk 17:48, 12 September 2005 (UTC)
thread_title:  Add topical navigation menu(s) to every Wikipedia page 

message: The recent changes of the monobook seem to hide some navigational boxes completely - e.g. Template:Provinces of Thailand. The main difference between that one and those which still show is that the invisible include a id="toc". Yesterday they still showed, however due to the caching of the css I'm not sure which change actually was the "bad" one. Where is the problem - within the css or the template? andy 11:09, 27 September 2005 (UTC)
replies: text: That template is visible to me - I'm using IE6.0 at the moment.  What's your browser? Worldtraveller 11:21, 27 September 2005 (UTC)
replies: text: Firefox 1.0.6 andy 11:22, 27 September 2005 (UTC)

text: Strange, now they are back, and nothing was changed in the css. andy 16:08, 27 September 2005 (UTC)
thread_title:  Navigationboxes not working anymore 

message: Looking at m:Link style vote the decided policy seems to be underlining links even when the mouse is not over a link, however I see that this behaviour has been reverted by ABCD. The justification he invokes is "allow browser settings to propagate". But, as you can see in monobook/main.css on line 66:
 a
 {
     text-decoration: none;
     ...
 }
This means that browser settings won't propagate, and that links will never be underlined, regardless of what the browser settings are. Note that this only occurs when not logged in (otherwise it depends only on the user's preferences), and that Firefox's Web Developer Toolbar confirms that this is indeed the reason why links are not underlined. Unless monobook/main.css can be modified to fix this, I believe this change should be reverted... Or maybe there was another discussion of this issue? (in which case m:Link style vote should be updated) --Ma Baker 02:08, 8 November 2005 (UTC)
thread_title:  underlined links? 

message: Since a large portion of people are color blind in some sense, we should address this quickly:
(copied from User talk:Jimbo Wales)
----
:Hi Mr. Wales, or Jimbo, which ever you prefer.
:I'm just inquiring about a recent change in the edit thingy. When you enter into "History" of an article & then click on the "Compare Selected Changes" button, the changes were shown in dark red. But now they are hardly visible, & for an editor with colourblindness, it is quite hard to see what changes people have made to the article. Could you please supply me with an answer if this will be changed or remedied or if it will stay the same.
:I would have posted this on the appropiate page, but I do not know of one, so selected you because you are the "Main Man" on Wikipedia I suppose.
:Regards, Spawn Man 23:15, 7 December 2005 (UTC)
thread_title: Need diff colors that are compatible with color-blind people

message: I was told that here is the place to say this, so sorry if it isn't. May I suggest the hearder be moved back to the top of the page where it used to be, rather than at the right of the page title. The first time I saw it like that I thought it was a bug; I really do think it looks terrible. If I'm understanding the code in the history correctly it's been changed and reverted, and it's only a test, but my view is don't keep it like this! Why was it moved to the right in the first place anyway? Raven4x4x 08:52, 23 December 2005 (UTC)
thread_title:  Site notice now to the right of page title 

message: In, Firefox, left-floated image boxes nearly overlap the text above.
I suggest that a margin-top is added:
div.thumb {
    margin-bottom: 0.5em;
    margin-top: 0.5ex;
    border-style: solid; border-color: White;
    width: auto;
}
--84.194.112.7 17:57, 11 January 2006 (UTC)
thread_title:  Margin around image box 

message: Can somebody revert the spoken code to:
 #spoken {
  display: block !important;
  border-bottom-style: none;
  float: right;
  position: absolute;
  right: 2%;
  top: 0.6em;
 }
The current code doesn't work.  Joe D (t) 13:50, 20 July 2005 (UTC)
replies: text: Requesting again, this never got done.  Joe D (t) 02:05, 17 January 2006 (UTC)
replies: text: Would this code work when there are announcements in the heading, like during the recent fundraiser or with Jimbo's appeal for donations? ~MDD4696 05:15, 17 January 2006 (UTC)
replies: text: Usually.  The modified code was supposed to make it change depending on the site notice, but merely broke it.  A simple temporary fix is easily implemented while the site notice is enabled. Joe D (t) 05:36, 17 January 2006 (UTC)
thread_title:  Spoken