4 commits

Author	SHA1	Message	Date
Jdlrobson	abf445ec9b	Revert "Minerva is responsible for turning on WikimediaEvents itself" ... While harmless, this patch is not needed if we take a different approach as discussed in https://phabricator.wikimedia.org/T204144#4612790 This reverts commit 01dc9de92e. Change-Id: Id2fdd8677042121142ab2663edfa0ee400b8bf22	2018-09-24 22:52:12 +00:00
jdlrobson	01dc9de92e	Minerva is responsible for turning on WikimediaEvents itself ... Unlike other skins, Minerva wants to be in charge of when WikimediaEvents is loaded, so that it can guarantee load order happens at a time that suits it. WikimediaEvents will be loaded after initialisation of the interface. This allows Minerva to enable schemas such as ReadingDepth conditionally. Upon merging this patch, Ibb45f40ea301727c0c6480043760bd9426106845 can be merged which will revoke WikimediaEvent's ownership. Merging in this order will ensure that ReadingDepth is never removed from production. Bug: T204144 Change-Id: If8395033f31485aca0ca3b38fda1be985369b481	2018-09-19 22:09:26 +00:00
jdlrobson	38474ed73f	Hygiene: Cleanup initialisation files ... * Remove deprecated module definitions * Remove unnecessary check for Minerva skin (this is only ever run by Minerva skin) * Move overlayManager to place it is first used * Make Skin::getMainMenu method redundant Change-Id: I17ea52172e7fae0a8f0e06b8418c7ed5bb01ef64	2017-09-07 17:48:58 +00:00
jdlrobson	2cc9516cde	Minerva is its own skin ... This is programmatic output from python3 scripts/migrate.py This will result in a Minerva skin dependent on MobileFrontend. Post merge we will rename message keys to have minerva- prefix Bug: T166748 Change-Id: Iff1f7e63e796cc5d4a6d2ab0370e0c33248d2fce	2017-07-12 08:12:40 -07:00