HTML formatting of the queue was distributed over several OutputPage methods. Each method demanding a snippet of HTML by calling makeResourceLoaderLink() with a limited amount of information. As such, makeResourceLoaderLink() was unable to provide the client with the proper state information. Centralising it also allows it to better reduce duplication in HTML output and maintain a more accurate state. Problems fixed by centralising: 1. The 'user' module is special (due to per-user 'version' and 'user' params). It is manually requested via script-src. To avoid a separate (and wrong) request from something that requires it, we set state=loading directly. However, because the module is in the bottom, the old HTML formatter could only put state=loading in the bottom also. This sometimes caused a wrong request to be fired for modules=user if something in the top queue triggered a requirement for it. 2. Since |
||
|---|---|---|
| .. | ||
| scripts | ||
| styleguide-template | ||
| Makefile | ||
| package.json | ||
| README.txt | ||
| styleGuideModules.txt | ||
The Makefile, package.json, scripts, styleguide-template, and mediawiki.ui/styleguide.md files and directories here and in resources/src/mediawiki.ui/ support the automatic generation of CSS documentation from the source LESS files using kss for node.js, https://github.com/kneath/kss To build and open in your web browser, run: MEDIAWIKI_LOAD_URL=mediawiki_hostname/w/load.php make kssopen For example, MEDIAWIKI_LOAD_URL=1.2.3.4/w/load.php make kssopen If MediaWiki is running on localhost, you can omit MEDIAWIKI_LOAD_URL. To rebuild without opening the web browser, run: MEDIAWIKI_LOAD_URL=mediawiki_hostname/w/load.php make When modifying styleGuideModules.txt, keep the list in strict alphabetical order (with no extra formatting), so CSS loads in the same order as ResourceLoader's addModuleStyles does; this can affect rendering.