Topic on Extension talk:MobileFrontend

so many wikis have something like "Navbox" on enwiki.

basically, this is (mainly) a horizontal box, located at the bottom of article. it does not live under its own section - typically just below the last section (e.g., "references").

however, logically it does not belong in the last section: just one out of several million example, see en:Copata, and the "La Paz Department" box below the references.

using "mobile view", this template is swallowed by the "reference" section, even though it does not belong there, so the mobile user, who might not be interested in looking at the references, does not even know they might be missing a lot of things which are not really references. on the other hand, with mobile view, the navbox loses the "colapsibility" it has with desktop view.

methinks the right thing to do is to introduce a new css class that will tell mobile view how to deal with navbox, and add this class to the navbox. note that navbox has mucco interwiki links - this template, or something very similar, exists in most or even all wikis.

peace.

This is a good point. Traditionally, there have been large groups of 'content' elements that have been below the last header, even though in terms of 'sections' they don't logically belong to that particular section. I have thought about this in the past and also for usability/accessibility purposes, it would be best if we added a special header between the last section and the 'footer' sections. Currently this is not the case however, and adding it would require huge amounts of edits in the wikitext, so short term, it's not really a good solution. I guess we could write some sort of 'detection' routine for the english wikipedia in the short term, but it doesn't really sound like a sustainable idea either. Elements that fall into the 'content footer' section of a Wikipedia article are generally: Navbox, Stub templates and succession boxes.

i think it makes sense to introduce a css class that would cause an element that contains it to behave "like a header" in the mobile view.

this will allow actual maintainers of each wiki to add this class to whatever element they want, without having any effect on desktop view.

doing it this way, it will suffice to add this class once to the "navbox" template - this is not, by any means, huge amount of edits.

peace.

This is a good point. I've opened https://bugzilla.wikimedia.org/show_bug.cgi?id=38246 I'm not quite sure how to do this - adding a class would not really be feasible here as what is happening is the mobile extension is splitting the article into sections based on the headings it encounters.

I believe in the meantime a Wiki editor could add a hidden heading to separate these sections e.g.

<!-- references text here --> <h2 style="display:none;"></h2> <!-- navbar here -->

of course, it goes without saying that just adding a css class will not suffice - obviously i was thinking "add a css class and teach the mobilview extension to treat an element with this class as if it resides in its own header" (we could, e.g., use the elemen's title or some other html attribute in lieu of the header text).

peace.