Resending now that I'm on the design@lists.wikimedia.org list.
On Tue, Sep 17, 2013 at 9:55 AM, Adam Baso abaso@wikimedia.org wrote:
There's been some additional discussion on this, taking search engine and Find in Page optimization into account.
https://bugzilla.wikimedia.org/show_bug.cgi?id=45951 https://bugzilla.wikimedia.org/show_bug.cgi?id=49202 (my duplicate with some Find in Page-oriented stuff)
The smart search engine / Find in Page stuff is moderately complex, so I think the tappable options for section expansion are the place to start.
It seems to me that the following achieves TOC-like information at a glance while balancing page load performance, usability, user choice, and user choice measurement:
- Don't auto-expand articles by default
- Do have a JavaScript-injected "Expand Sections" / "Collapse Sections"
feature at the top of articles with multiple sections
- Do have a user preference for Auto-Expand Sections on Article Load.
- To gauge love/hate for features, have two preferences as follows
*Show 'Expand/Collapse Sections' Option at Top of Articles* On / Off (default = On)
*Auto-Expand Sections on Article Load* *Note: this may slow page load time* On / Off (default = Off)
On Mon, Sep 16, 2013 at 4:20 PM, Jared Zimmerman < jared.zimmerman@wikimedia.org> wrote:
I like the idea of expanding by default because it fixes my pet peev of not being able to do a find on page from my mobile browser without first expanding all sections.
*Jared Zimmerman * \ Director of User Experience \ Wikimedia Foundation M : +1 415 609 4043 | : @JaredZimmermanhttps://twitter.com/JaredZimmerman
On Mon, Sep 16, 2013 at 12:52 PM, Mathieu Stumpf < psychoslave@culture-libre.org> wrote:
I didn't followed the thread, but if you try to consult the french wiktionary with the mobile interface it's impossible: section title are links so when you try to uncollapse them, you follow the link.
Le lundi 16 septembre 2013 à 11:05 -0700, Brion Vibber a écrit :
On Mon, Sep 16, 2013 at 10:51 AM, Arthur Richards arichards@wikimedia.org wrote: If we still want to explore dynamically loading article sections (which we all seemed to be in favor of when we did annual planning back in June), it's hard for me to imagine how we could realistically pull that off if we display sections uncollapsed as default.
We could rig up an "infinite scroll" type of situation, where we basically:
load section 0 and section 1
leave placeholder <div>s for sections 2 and beyond
when the user scrolls down into section 1, start loading section 2
in the background
** prepare the same thing for the bottom of section 2 load section 3, etc...
Of course a problem with this setup is that if you go offline partway through reading the article, the later sections might be unavailable when you scroll down to them.
-- brion
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l