Forum:IE fixes in main.css

Hi.

It's about the main.css, which is commons to all wikis. Actually, Is not a important problem but it's only to report it.

First of all, I use SeaMonkey 1.1 which has the Gecko engine of Firefox 2.0 so I think that the problem is for that program too. The SeaMonkey has a console which warns if there was a problem in CSS or JavaScript when a page is loaded. I usually use it for testing my custom .js and .css, as well for the main ones of Inciclopedia and Wikijuegos.

Sometime ago, It started to warn about the lines 1244, 1245, 1246 of this file on every page loaded. I was ignoring them until now, but I research what happens.

The code is this: (in bold the lines reported) /* more IE fixes */ /* float/negative margin brokenness */ * html #footer {margin-top: 0;} * html #column-content { display: inline; margin-bottom: 0; } * html div.editsection { font-size: smaller; float: right; margin-left-value: 5px; margin-left-ltr-source: physical; margin-left-rtl-source: physical; }

I never see "value" or "ltr" after "margin-left" in CSS, but I suppose that they are CSS3... After see a little more this file, I saw that all IE Fixes in this file has the following format: * > html #NameOfClass

So, I think that the greather than character " " was missed when this classes were added -- 10:55, 3 February 2007 (UTC)


 * The problem is that:

margin-left-value: 5px; margin-left-ltr-source: physical; margin-left-rtl-source: physical;
 * ...are not valid CSS. They are internal pseudo-css for some mozilla/wysiwyg editor or something. I'll ask for their removal. --Splarka (talk) 12:57, 3 February 2007 (UTC)


 * Update: On the to-fix list. This example actually ended up as a training session for the comteam on the new bug report system.. Thanks ^_^ --Splarka (talk) 09:17, 11 February 2007 (UTC)

I'd actualy like a method of allowing Sysops the ability to add browser specific css fixes to different wikia. My opera glitch on The Gaiapedia can start to get annoying. And I can't fix it and support Opera because if I do, then Safari, OmniWeb, Konqueror, and every other KHTML/WebKit browser will break in the wiki. I did come up with an idea on how to allow this to be done. But I've been waiting on the head of the browsecap.ini project. Dantman (Talk) 12:58, 4 February 2007 (UTC)


 * Not sure how that could be done without being difficult... --Splarka (talk) 09:17, 11 February 2007 (UTC)


 * It's actualy exceedingly simple. I already have it setup in a small project that I haven't gotten back to working on. http://dantman.awardspace.com/apsigs if you notice the browser display test there, it renders differently in IE, Firefox, and Opera. And if you open up the source for the page you'll notice that in the body's class tag some extra little info is added in. Right now I get class="opera 9_1 9 winxp", and the code is quite simple, thanks to the browsecap.ini project.

function browserClass { $b = php_get_browser; $c = str_replace( ".", "_", $b['browser'] ); $c .= " ". str_replace( ".", "_", $b['version'] ); $c .= " ". str_replace( ".", "_", $b['majorver'] ); $c .= " ". str_replace( ".", "_", $b['platform'] ); return strtolower( $c ); } This is the function that returns the output I put into the class tag. php_get_browser is just a function that someone created to replace php's native get_browser function because php's native function requires the php_browsecap.ini file to be specified in php.ini, and most shared hosts don't keep that up to date. The only thing that the wikia devs would half to do to keep this working, would be to add the function so that it is added to the class by placing a echo for that function in the Monobook.php skin (replacing php_get_browser with get_browser if they want to use the native function), and they'd just half to keep their php_browsecap.ini file up to date from here. I actualy created a small script for my system which would update a php_browsecap.ini file inside of the installation of the system. It would be quite easy for me to convert the entire css browser detection system to work in MediaWiki, because my coding style has been highly influenced by working with MediaWiki, so much that my project there works in some similar ways to MediaWiki.
 * Although, it is highghly possible that we're overlooking the fact that Monobook.css comes from MediaWiki:Monobook.css, meaning it's a page using wikitext. It's possible we could actualy setup a  type of thing if we wanted. Dantman (Talk) 10:24, 11 February 2007 (UTC)


 * While it is an (ahem) original solution, it is not one I would advise implementing. For example, in one older browser I get:


 * Which introduces several ambiguous and at least one conflicting class name... Furthermore, when we upgrade to 1.9, we will have many more classes added to the body tag by the vanilla MediaWiki code, for example:


 * this then would produce something akin to:


 * which is not simplifying things. I would suggest you suggest a more sanity-based, less verbose, and clarified implementation upstream, possibly to Wikipedia:User:Simetrical, possibly a single class such as,  ,   (you get the idea). --Splarka (talk) 11:58, 11 February 2007 (UTC)