Page MenuHomePhabricator

Special:MobileLanguages should be in core and called Special:Languages
Open, NormalPublic

Description

The Minerva skin minimises payload by not serving languages in the page and instead opting to use JavaScript to load other languages or for those without JavaScript a special page fallback.

The parameter given to the page is the page to retrieve languages from.
For example:
https://en.m.wikipedia.org/wiki/Special:MobileLanguages/San_Francisco

Problems

The Minerva skin currently has to depend on the MobileFrontend extension to get the fallback functionality.

Notes

This is one of many non-standard language selectors which need to be consolidated; see also T73136: Improve language selection.

Event Timeline

Jdlrobson claimed this task.
Jdlrobson raised the priority of this task from to Lowest.
Jdlrobson updated the task description. (Show Details)
Jdlrobson added subscribers: Glaisher, Moushira, Tgr and 11 others.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 2 2015, 11:44 PM

Maybe we can use this as a fallback for non-JavaScript clients when the current interlanguage list is replaced with a compact language selector. Before that happens I think you would be the only user of the special page.

Nemo_bis updated the task description. (Show Details)Jul 8 2015, 9:32 AM
Nemo_bis set Security to None.
Nemo_bis added a subscriber: Nemo_bis.

Jon, it would be useful to clarify what MobileFrontend's requirements are before it can use a standard language selection facility such as jquery.uls or the ULS interlanguage links.

@Nemo_bis mainly it solves the problem of the large amount of HTML generated by supporting up to 200 languages. In mobile we aim to reduce the HTML we send down the wire as much as we possibly can and we do this by using JavaScript (currently a mobile specific module but there is no reason with some work it couldn't use ULS). This would help skin developers in the mean time as it will allow them more flexibility about how they surface languages.

This would be a non-JavaScript fallback. As @Nikerabbit states in the future this could be used for ULS.
We currently have this use case, so I'd be keen to get this more visible so when @Nikerabbit needs it is available and no one re-invents the wheel.

Not sure why the thumbs down from @Ricordisamoa - I'm not sure how making languages more accessible is a bad thing.

kaldari removed a subscriber: kaldari.Aug 14 2015, 1:34 AM

Not sure why the thumbs down from @Ricordisamoa - I'm not sure how making languages more accessible is a bad thing.

"Compact interlanguage links" only work with JavaScript, so I'm not sure why desktop users need a non-JavaScript fallback.

MaxSem removed a subscriber: MaxSem.Aug 17 2015, 7:43 PM

the large amount of HTML generated

AFAIK, this assumption about large amounts of HTML has never been field-tested. What's the actual payload and what is the threshold that must not be crossed?

This would be a non-JavaScript fallback. As @Nikerabbit states in the future this could be used for ULS.

MobileFrontend developers could/should submit patches for https://github.com/wikimedia/jquery.uls to have such HTML fallback, especially as you already have Special:MobileLanguages as starting point.

MobileFrontend developers could/should submit patches for https://github.com/wikimedia/jquery.uls to have such HTML fallback, especially as you already have Special:MobileLanguages as starting point.

That makes no sense as jquery.uls is library written in JavaScript. Did you mean the ULS extension?

Jdlrobson moved this task from Backlog to Tasks on the MobileFrontend board.Nov 4 2015, 5:01 PM
Nemo_bis edited projects, added I18n; removed Language-Team.Dec 5 2015, 10:57 AM
Danny_B moved this task from Unsorted to Move on the Technical-Debt board.Jan 23 2016, 1:25 AM
Jdlrobson moved this task from Tasks to Tech debt on the MobileFrontend board.Feb 18 2016, 6:43 PM
jhobs raised the priority of this task from Lowest to Normal.Dec 1 2016, 9:42 PM

This proposal is selected for the Developer-Wishlist voting round and will be added to a MediaWiki page very soon. To the subscribers, or proposer of this task: please help modify the task description: add a brief summary (10-12 lines) of the problem that this proposal raises, topics discussed in the comments, and a proposed solution (if there is any yet). Remember to add a header with a title "Description," to your content. Please do so before February 5th, 12:00 pm UTC.

This got 10 votes in the wishlist (#43) @Tgr is this something we could work with you to achieve this quarter?

Tgr added a comment.Mar 6 2017, 10:47 PM

@Jdlrobson to me a special page does not seem all that useful since most pages wouldn't want to show a bare languages page (it makes sense for a minimalistic mobile view but in general it's not great UX) but rather some kind of dynamcally loaded content like Compact Language Links does. Maybe a set of helper classes that can render a partial or full list of languages or return structured data about them, so that MobileFrontend can create a special page with a minimal amount of boilerplate code, and ULS can reuse it?

Jdlrobson moved this task from Backlog to Later on the Readers-Web-Backlog (Tracking) board.