Perhaps as an improvement as to how we actually load CSS and JS files.
85% of that kind of ordering is currently done inside of the Skins. And
not only that, but when a new skin like Modern comes out, it just goes
and duplicates what Monobook does. And even worse, there are the user
made skins elsewhere. Those just copy what Monobook does at some point,
and never get updated if we ever change that.
Additionally, it's quite ugly when you get into things extensions load.
Namely if they were created to load a global css/js for a wiki farm.
Those extensions have little control over where that stuff is actually
loaded, and not only that but if you actually want to have that proper
control, the alternative is to just hack the skins you're using. Kinda
ugly (This is the one of the reasons I have my own dedicated skins repo).
Perhaps we could improve the system by making generation of the list of
css/js files to load (and what order to load them). Something like a
system where we identify script/style dependencies and have the system
automatically order them. In addition to that, we could identify things
like if they should be conditional (for IE primarily...) to make it
easier to add new fixes files.
The primary relevance here, is that it's easier to create a system that
does automatic creation and ordering of the files if they just generate
a stack of script and link elements.
One of my ToDo's was improving MediaWiki's support for script libraries
and stuff like jQuery, YUI, Scriptacious, etc... Part of that was also
adding in a bit of support for allinone because these commonly end up
loading multiple extra js/css files, and it piles up the HTTP Requests.
~Daniel Friesen(Dantman) of:
-The Nadir-Point Group (
http://nadir-point.com)
--It's Wiki-Tools subgroup (
http://wiki-tools.com)
--Games-G.P.S. (
http://ggps.org)
-And Wikia ACG on
Wikia.com (
http://wikia.com/wiki/Wikia_ACG)
Brion Vibber wrote:
Huji wrote:
Actually, using @import has another side effect
too: When saving the page,
not all CSS is saved (depends on browser, of course). Using link makes sure
that all CSS is going to be saved.
So unless a robust technical reason is given, I'm in support of getting rid
of @imports (only because they're supported and classy, doesn't mean they
should be used).
It's to keep Netscape 4 from loading the CSS2 stylesheets, freaking out,
and becoming completely unusable because it thinks it knows CSS2 but was
so woefully bad at it that it just messes everything up.
In these days where Netscape 4 is pretty much dead, we might consider
dropping that -- at least if there actually *is* a measurable
improvement to doing so.
-- brion
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l