tested on android-4.1, standard browser chrome.

This is not a blocker at all - it looks like a request for enhancement to me.

See https://www.mediawiki.org/wiki/Bugzilla/Fields#Severity

This is not a Collection bug, Special:Book works perfectly on mobile. The issue is MobileFrontend killing links to it too aggressively. https://en.m.wikipedia.org/wiki/Special:Book

bingle-admin wrote:

Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1963

Not sure what actions there are here. We could potentially add a link to the bottom of the page in alpha as a starting point to explore interest but before that can happen the Special:Book page looks poor.

If it was rewritten to use HtmlForm it would look much better in mobile. Patches for that welcomed!

@Nemo_bis T65459 concerns adding the Book link to the menu.
if Special:Book does not work in mobile that is a problem with the extensions collection
I don't see how any of this is specific to MobileFrontend - there is nothing to do here :-)

In T62249#990342, @Jdlrobson wrote:

@Nemo_bis T65459 concerns adding the Book link to the menu.

Not really. That bug is more general; I tentatively marked it as blocker as you say it's related. *This* bug is about adding the Book link to the menu.

if Special:Book does not work in mobile that is a problem with the extensions collection
I don't see how any of this is specific to MobileFrontend - there is nothing to do here :-)

How so? Are you saying the addition of the link to Special:Book doesn't require a patch to MobileFrontend?

Updated the title to reflect the actual task description.

Is there a bug for making Special:Book work on MobileFrontend ?

I have setup T87400 and T87399 as starting points.