Hi, I have been playing with the app some more and I think I have found a simpler change that will solve the issue for me.
When I am scrolling down a page such as WP:GAB, the navbar at the top of the page disappears, which takes the TOC icon away with it. I was finding it easy to get lost in a mass of text when scrolling down the page; hence my request for collapsed sections. However when I scroll up the navbar reappears. Can you make the navbar remain visible at all times? I have other feature requests but this would be the most important right now. Other requests: * Facilitate the viewing of page history within the app * Allow images to be disabled * Facilitate easy access to the Refdesk, Teahouse, and other help resources for both readers and editors Thanks, Pine Pine *This is an Encyclopedia <https://www.wikipedia.org/>One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future,The clear water we must leave untainted for those who come after us,The fertile earth, in which truth may grow in bright places, tended by many hands,And the broad fall of sunshine, warming our first steps toward knowing how much we do not know.* *—Catherine Munro* On Mon, Oct 20, 2014 at 9:37 AM, Moiz Syed <[email protected]> wrote: > Another good reason for not collapsing the sections in the content area is > because of the Table of Contents flyout. Having collapsed sections in the > content area will make the TOC flyout redundant. We wanted to address the > need for collapsed sections by giving an easy access to TOC. > > On Mon, Oct 20, 2014 at 9:19 AM, Vibha Bamba <[email protected]> wrote: > >> Thank Pine, >> I believe its first critical to understand why a user needs this. >> We have to understand a user's need instead of responding to an interface >> request. >> There may be better ways of serving the same need. Typically one user >> group tends to think for themselves, but as a UX team, we need to serve the >> needs of users across the board. >> Kindly explain. >> >> Thanks >> Vibha >> >> ---- >> Vibha Bamba >> Senior Designer | WMF Design >> >> >> >> >> >> >> >> On Sun, Oct 19, 2014 at 7:55 PM, Pine W <[email protected]> wrote: >> >>> Hi Vibha, >>> >>> Um.... If a customer is asking about a possible feature change then I >>> would ask you to AGF, please. The change may be impossible to implement, >>> there may be good reasons for the status quo, there may be reasonable >>> differences of opinion, etc. In this case I am saying that I think there is >>> a reason to collapse sections even with the TOC flyout, and I have offered >>> an example of a page where this would be helpful. I would appreciate an >>> explanation of how this would break the TOC structure. >>> >>> Thank you (: >>> >>> Pine >>> On Oct 19, 2014 6:43 PM, "Vibha Bamba" <[email protected]> wrote: >>> >>>> We can't collapse sections on the app, that would be pointless and >>>> would completely break the structure of the TOC. >>>> >>>> >>>> ---- >>>> Vibha Bamba >>>> Senior Designer | WMF Design >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Sun, Oct 19, 2014 at 2:26 AM, Federico Leva (Nemo) < >>>> [email protected]> wrote: >>>> >>>>> Pine W, 19/10/2014 08:28: >>>>> >>>>>> Would it also be possible to have sections collapsed by default, as >>>>>> happens on mobile web? >>>>>> >>>>> >>>>> Did you read the archives first? >>>>> http://thread.gmane.org/gmane.org.wikimedia.mobile/1045 >>>>> http://thread.gmane.org/gmane.org.wikimedia.mobile/507 >>>>> >>>>> Nemo >>>>> >>>>> _______________________________________________ >>>>> 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 >> >> >
_______________________________________________ Mobile-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mobile-l
