https://bugzilla.wikimedia.org/show_bug.cgi?id=45229
--- Comment #7 from Krinkle <[email protected]> --- Note that one reason to do sort them alphabetically is to share cache between pages. This is why mw.loader.load calls outputted by the server as well as the actual http requests made my mw.loader always sort alphabetically, since implementation ensures proper execution order. When code adds things using addModuleStyles that aren't order-sensitive per se, this keeps them consistently in the same order regardless of whether two pieces of code execute in a slightly different order (e.g. as result of refactoring in the caller, or, changing the order in which hooks are registered when you reorder things in LocalSettings.php, etc.). That can all lead to inconsistencies (e.g. if a module is loaded on a Special page via hook, and in the parser on regular pages, if those happen in different orders then they wouldn't consistently load after or before the skin). So I can imagine it may be interesting to investigate the possibility of keeping the forced sort with the option to perhaps hoist important ones in a fixed order. Anyway, that opens another can of worms and an arms race of sorts, so let's not for now :) -- 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 [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
