On 12/10/2010 01:48 AM, jidanni(a)jidanni.org wrote:
I there any list of halfway implemented CSS?
E.g.,
(rgrep "allpagesredirect" "* .*" "~/mediawiki/" nil);
emacs
./includes/specials/SpecialAllpages.php:337: $link = ( $s->page_is_redirect ?
'<div class="allpagesredirect">' : '' ) .
./includes/specials/SpecialPrefixindex.php:161: $link = ($s->page_is_redirect ?
'<div class="allpagesredirect">' : '' ) .
is halfway implemented because it only appears in the .php files, but
not in the standard CSS files.
So allpagesredirect is #1, redirect-in-category is #2, where is the
complete list of them, and how one best should use them?
I was the one who added redirect-in-category (allpagesredirect existed
before) in r22156. It's been a few years, but I think I left it
unstyled by default both because allpagesredirect was that way already,
and because I didn't want to get tangled up in endless debates about the
appropriateness of the interface change.
I certainly wouldn't object to making both of those classes italicized
by default in MediaWiki. Some sites do style them differently (for
example, I think Commons makes them both small _and_ italic), but
italics seem to be nearly universal among sites that style them at all,
and those who don't want them can always override it.
/** Use the full set of CSS bindings, like Wikipedia
does, without
having to put them into Mediawiki:Common.css and maintain them on
every single site of our WikiFamily. */
$wgUseFullCss = true;
https://bugzilla.wikimedia.org/show_bug.cgi?id=26266
It might be useful to have collections of popular but not universally
desired CSS styles (whether provided by us or by third parties)
available for convenient installation.
Technically, one could already turn a style sheet into an extension by
bundling it with a short PHP file, but that's still unnecessarily
complicated. It would be better if we could just tell wiki owners to
download the CSS file and drop it into the right (common or
skin-specific) directory, and it'd automagically start to work.
Something for the ResourceLoader folks, maybe? Or does such a feature
already exist?
--
Ilmari Karonen