Page MenuHomePhabricator

Unknown dependency: when trying to use Minerva on desktop
Closed, ResolvedPublic1 Estimated Story Points


When visiting the desktop version of Minerva via @Esanders points out an error is thrown in the console.

The error is:

load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin…:177 Error: Unknown dependency: Error: Unknown dependency:
    at sortDependencies (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin…:159)
    at resolveStubbornly (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin…:160)
    at Object.load (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin…:171)
    at Main_Page?useskin=minerva:10
    at startUp (load.php?debug=false&lang=en&modules=startup&only=scripts&skin=minerva:79)
    at HTMLScriptElement.script.onload.script.onreadystatechange (load.php?debug=false&lang=en&modules=startup&only=scripts&skin=minerva:80) should only load on the mobile site as it is a direct replacement for common.js

Please move this logic:
into the MobileFrontend extension inside the onBeforePageDisplay when operating in mobile mode.

Acceptance criteria

  • should load for all skins when useformat=mobile is applied.

e.g. Vector, | Minerva.

  • should not load when useformat=desktop is applied. site should load instead.

Event Timeline

Should load for all skins and all MF pages, or just Minerva?

Thanks. I commented out to test, and the next exception thrown is on this line in skins.minerva.editor/init.js

if ( mw.config.get( 'wgIsMainPage' ) || isNewPage || page.getLeadSectionElement().text() ) {

Where getLeadSectionElement returns null.

Yes I used to subscribe to those groups. But now I just do a (w)diff of
RELEASE-NOTES. Alas the mobile stuff has no RELEASE-NOTES like files.
Please add them.

Also next time be sure to post in

The error message just looks like a common error message. Like the
administrator did something wrong.

The error message should say


Please tell your wiki Administrator, we have changed ...
so you should change ...
to get your wiki back working. (No this is not a ransom message.)


Had you not had very visible exceptions, it would have been assumed you redesigned your mobile site.

If it looked the same, then nobody would think I redesigned the site.
If it looked different, then people would think I redesigned the site, no?

Anyway I'm not sure, but I think now that I added
$wgMFDefaultSkinClass = "SkinVector";
my site thankfully looks the same.

I recall
$wgMFDefaultSkinClass = "SkinMinerva";
was the default for Wikipedia, but I'm not Wikipedia.

Although I always like to stay on the recommended track and would
like to upgrade to MinervaNeue however I couldn't even get the editor to
start, T172643 , so maybe I'll wait till all the bugs are worked out.

Yes after each installation I now should check

  • a random desktop page
  • a random mobile page
  • editing in desktop
  • editing in mobile.

I was only doing the first.

Jdlrobson raised the priority of this task from Medium to High.EditedAug 8 2017, 5:40 PM

If it looked the same, then nobody would think I redesigned the site.
If it looked different, then people would think I redesigned the site, no?

It would look different if you used Minerva as your skin e.g. would look like

$wgMFDefaultSkinClass = "SkinVector";
my site thankfully looks the same.

I'm not sure I follow. Are you saying your mobile site uses (and has always used) the Vector skin? If so, I have to ask why you were using MobileFrontend before this change. Doesn't sound like you need it. (your mobile site) looks exactly the same as to me. Is this intentional? If so you don't need MobileFrontend...

On the other hand, the Minerva skin looks like it's working perfectly fine to me:
This particular bug only impacts the desktop version of the skin which you are not using.

I recall I was using MobileFrontend because way in the past that was the only way to accommodate mobile users. Now that apparently vector can handle mobile too, OK I'll try removing MobileFrontend..

it's worth taking a read through the updated - if you want a different skin for mobile, then you probable do want MobileFrontend. Edit button seems to work fine for me on . I have commented on the relevant ticket.

I am sorry. I think I have three bugs here. I think some of them are merged. When I post a reply it seems to end up getting posted on a different one of these bugs. Maybe I often paste to the wrong browser window. Forgive me.

Yes I want to do what Wikipedia does, as that looks good. So I'll put back Minev... skin soon.

Change 371498 had a related patch set uploaded (by Jdlrobson; owner: Jdlrobson):
[mediawiki/skins/MinervaNeue@master] MobileFrontend should be responsible for adding module

Change 371499 had a related patch set uploaded (by Jdlrobson; owner: Jdlrobson):
[mediawiki/extensions/MobileFrontend@master] Load on all mobile skins

Fix is trivial and it's bothered a few people now so I'd appreciate a review of if anyone has some spare time!

Jdlrobson set the point value for this task to 1.

Change 371499 merged by jenkins-bot:
[mediawiki/extensions/MobileFrontend@master] Load on all mobile skins

Change 371498 merged by jenkins-bot:
[mediawiki/skins/MinervaNeue@master] MobileFrontend should be responsible for adding module