am 10.08.2009 00:53 schrieb Platonides:
Peter Velan wrote:
--- Still differences between internal/external ---
I changed the iconic images for pdf, audio, video, (and added some more for .odp, odt, .zip, etc.), but the new CSS-setting in "MediaWiki:Common.css" is used for styling of internal links only. external links are still styled with data found in main.css.
Only after completely commenting out "a.external ..."-section in /skin/modern/main.css the internal and external links are styled identically.
The declarations with .external are more specific, that's why they're being used, You can make your define work for both, ie. #bodyContent a.external[href $=".pdf"], #bodyContent a[href $=".pdf"]...
Works - thanks!
--- Works not in monobook ---
My own prefered skin is "modern" (but the majority of our users goes with monobook standard). I was not able to achieve my goals in monobook :-( Whatever I tried, not one link is shown with epected style.
I took a deeper look to the brwoser output with Firebug and I see that in "modern" the content of MediaWiki:Common.css is read, but in monobook it looks like there's no MediaWiki:Common.css and even after I copied the news stuff into /skins/monobook/main.css I don't see the expected result.
What I'm doing wrong?
Bypass your cache.
Whatever I tried to eliminate cache-related things, I failed! Then I discovered this:
In modern/main.css the related styles defined like ...
#mw_content a[...]
... in all *other* supplied skins (including monobook) the definitions look line ...
#bodyContent a[...]
I duplicated every "#mw_content a[...]"-definition (needed for modern) in Common.css as "#bodyContent a[...]" (needed for all other skins) and finally it works :-)
Could somebody explain, why there's different style definitions (#mw_content vs #bodyContent)?
Peter
First there was nothing...
...and then MediaWiki showed up. ;-) I can't find the link where I read first about all the skins, but possibly it is somewhere on MediaWiki.org actually; Monobook was created far before modern was. 'myskin', 'monobook' and some more skins looks pretty the same, but modern was created in 1.12 < http://www.mediawiki.org/wiki/Manual:$wgDefaultSkin%3E and uses other id's; therefore, modern uses it's own common, print and such .css'es.
See also en-wikipedia's: http://en.wikipedia.org/wiki/Special:Gadgets and http://en.wikipedia.org/wiki/MediaWiki:Gadget-modernskin-thunks.js
Your's faithfully, D.D. (Sumurai8) http://www.wikikids.nl -- De Nederlandstalige encyclopedie door en voor kinderen
am 10.08.2009 14:46 schrieb Sumurai8 (DD):
Peter Velan wrote:
In modern/main.css the related styles defined like ...
#mw_content a[...]
... in all *other* supplied skins (including monobook) the definitions look line ...
#bodyContent a[...]
I duplicated every "#mw_content a[...]"-definition (needed for modern) in Common.css as "#bodyContent a[...]" (needed for all other skins) and finally it works :-)
Could somebody explain, why there's different style definitions (#mw_content vs #bodyContent)?
First there was nothing...
...and then MediaWiki showed up. ;-) I can't find the link where I read first about all the skins, but possibly it is somewhere on MediaWiki.org actually; Monobook was created far before modern was. 'myskin', 'monobook' and some more skins looks pretty the same, but modern was created in 1.12 < http://www.mediawiki.org/wiki/Manual:$wgDefaultSkin%3E and uses other id's; therefore, modern uses it's own common, print and such .css'es.
See also en-wikipedia's: http://en.wikipedia.org/wiki/Special:Gadgets and http://en.wikipedia.org/wiki/MediaWiki:Gadget-modernskin-thunks.js
Thank you. Will take a deeper look to above stuff.
Peter
mediawiki-l@lists.wikimedia.org