Last modified: 2014-02-27 22:10:20 UTC
Created attachment 14604 [details] Screenshot of <https://en.m.wiktionary.org/wiki/wildcard> on an iPhone, 2014-02-16 The MobileFrontend + Wiktionary user experience is pretty rough. Screenshot of <https://en.m.wiktionary.org/wiki/wildcard> on an iPhone attached. The page almost looks broken. There's only a single language for this entry yet it's collapsed. Owww. Given that MobileFrontend is the default for mobile devices, I think this is fairly high priority.
On the surface, this could be an argument for special-casing certain wikis to not collapse sections by default, *or* to apply some intelligence (perhaps on all wikis): If there is is only 1 section, uncollapse; If there are 3 or fewer sections, collapse 2 and 3 but uncollapse 1; If there are 4+ sections, retain current behavior.
Wiktionary uses sections differently from everything else, it seems, and doesn't use the lead section as expected. :) Could probably make section autocollapsing into a site config variable and switch it off for Wiktionary, but I should warn that what Wiktionary really needs is a structured data backend and an appropriate query & display interface that's custom-done for a multilingual dictionary.
Change 113758 had a related patch set uploaded by Brion VIBBER: Add $wgMFCollapseSectionsByDefault config var to allow disabling auto section collapse https://gerrit.wikimedia.org/r/113758
Right, you'll still have problems with user experience if all you do is just uncollapse section 1. Generally, the most important information, which a user expects to see unhidden by default, is the list of definitions. The top-level section will be a language header (like ==English==), but you'd still want to keep the less important subheaders within that section, like Etymology and Translations collapsed, or else it will drown out the more important info. I don't know if there is currently any programmatic way to identify which header corresponds to the part of speech (where the definitions are); here is the list of accepted ones in en.wikt: <https://en.wiktionary.org/wiki/Wiktionary:POS#The_part_of_speech_header_in_English>. There needs to be some configurability for other Wiktionaries, too. (In reply to Brion Vibber from comment #2) > Wiktionary uses sections differently from everything else, it seems, and > doesn't use the lead section as expected. :) > > Could probably make section autocollapsing into a site config variable and > switch it off for Wiktionary, but I should warn that what Wiktionary really > needs is a structured data backend and an appropriate query & display > interface that's custom-done for a multilingual dictionary.
Change 113758 merged by jenkins-bot: Add $wgMFCollapseSectionsByDefault config var to allow disabling auto section collapse https://gerrit.wikimedia.org/r/113758
