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.
On a more personal note, I really value the collapsed sections since we don't display a ToC on the page - so the collapsed sections essentially replaces the ToC for quick article navigation. I would find the site less usable if we uncollapse sections by default and do not otherwise expose a ToC. On Mon, Sep 16, 2013 at 10:46 AM, James Alexander <[email protected]>wrote: > I think this is more a design question so I generally concede to whatever > the mobile/design team thinks but as a user I really like the auto > compressed nature not because of the loading situations but because of > navigation on the phone. It makes it significantly easier to navigate > around the page and find what I want (a built in much easier to user toc > essentially) and helps my screen feel less cluttered as I read. I can > understand the 'they don't toggle the lower sections' argument but on a > personal level I'd agree with Brion, I often don't toggle the lower > sections just because my question is already answered (main facts are > almost always purposely pushed into the into and early sections) and am > unlikely to read them more because they're uncollapsed. > > James > > James Alexander > Legal and Community Advocacy > Wikimedia Foundation > (415) 839-6885 x6716 @jamesofur > > > On Mon, Sep 16, 2013 at 10:34 AM, Jon Robson <[email protected]>wrote: > >> + design-l >> >> On Mon, Sep 16, 2013 at 10:34 AM, Jon Robson <[email protected]> wrote: >> > The more I think about it, the more I think, in its current state >> > mobile should not collapse sections by default. If you really want to >> > find a lower section, scrolling down the page and being able to >> > collapse a section to see the next one is easy, yet if you just want >> > to read the article in its entirety it is annoying to have to click to >> > expand a section. >> > >> > Since we currently load all the HTML for the content of a page it >> > seems silly to hide it (although we should certainly rethink this if >> > we ever begin to lazy load sections) >> > >> > We ran event logging on toggling a while back [1] and the data showed >> > as you got down the page, it was less likely a section would be >> > toggled opened and read. >> > >> > I would propose we keep toggling enabled but change the default of all >> > sections to be open rather than closed. >> > >> > This also removes the existing risk of a flash of unstyled content and >> > enables the ability for users to do find on this page. >> > >> > We should at least run some kind of A/B test that rethinks this. >> > >> > Thoughts? >> > >> > [1] https://www.mediawiki.org/wiki/Event_logging/Mobile#Section_toggles >> >> _______________________________________________ >> Mobile-l mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/mobile-l >> > > > _______________________________________________ > Mobile-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/mobile-l > > -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687
_______________________________________________ Mobile-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mobile-l
