Timo Tijhof d5ed2785fb API: Include setupSkinUserCss in prop=modules for useskin mode ... Follows-up 90c95fc7f2, which included result of Skin::getDefaultModules in the prop=modules list. All hardcoded modules in OutputPage and Parser were also subsequently moved into Skin::getDefaultModules. However, a number of modules cannot be moved there because fundamentally Skin::getDefaultModules can only load modules via OutputPage::addModules(). For style modules, addModuleStyles() must be used. Fortunately, there is already a centralised place for that, namely Skin::setupSkinUserCss(). Include that in the ApiParse return as well. That should resolve the last bit of inconsistency between ApiParse and OutputPage when it comes to the module queue. Bug: T140664 Change-Id: I35e2e3bbdccdd1aa2a259b8e624daa80c609ba8c		2017-10-25 02:16:01 +01:00
..
common	Split Revision tests into Unit & Integration classes	2017-10-13 14:46:36 +01:00
integration/includes/http	Improve some parameter docs	2017-09-10 20:32:31 +02:00
parser	Allow duplicate articles in parser tests with same content	2017-10-01 21:23:17 +00:00
phan	build: Updating mediawiki/mediawiki-codesniffer to 13.0.0	2017-09-25 17:31:56 +02:00
phpunit	API: Include setupSkinUserCss in prop=modules for useskin mode	2017-10-25 02:16:01 +01:00
qunit	RCFilters: refactor highlight state	2017-10-19 19:28:41 +00:00
selenium	Selenium tests should log in before creating pages	2017-10-03 11:46:01 +02:00
.htaccess