--- Comment #5 from Platonides <> 2010-11-01 18:57:11 UTC 
I am not convinced about the usecase for adding such parserfunction in core.

You want to give a slightly different style to a table (eg. footballer infobox)
depending on the skin. Given how these things expand, this would ultimately
lead to hundred of pages with skin variants.
However, there's another way to get the same effect which doesn't require
splitting the cache: use a class in the infobox, then customize the styles in
MediaWiki:Vector.css, MediaWiki:Monobook.css...

I don't think there will be too much use for message customization either. Take
into account that internal messages can provide the skin as a parameter if
needed, so only wiki instruction would need it.

However, it reduces reviewing. An addition of
{{#ifeq:{{CURRENTSKIN}}|cologneblue | <profanity here> }} inside a biography
would be hardly noticed unless viewing the wikitext, while still providing the
vandal a way to advertise it using the useskin parameter.

Skin style customization via the skin css page, although harder for non-admins,
is much safer.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.

Wikibugs-l mailing list

Reply via email to