Whoops this was meant to be to the public mailing list! ---------- Forwarded message ---------- From: Jon Robson <jrobson(a)wikimedia.org> Date: Wed, Aug 27, 2014 at 2:39 PM Subject: Non-JavaScript Flow: Hiding non-ready functionality To: "Editor engagement list for the core E2 development team." <e2(a)lists.wikimedia.org> I noticed in a code review today that S was confused to why actions are unavailable in titlebar and posts (.client-nojs .flow-menu" has display:none in CSS) Recently in the last retrospective the Flow team agreed to record on the mailing list decisions, and since this decision happened prior to the meeting (about 3/4 weeks ago) I should try my best to record that decision. May, Danny, Shahyar and I sat down and spoke about the non-JavaScript version of the site, in particular with respect to mobile, as many mobile devices on slow connections will hit the non-JS site at some point. The summary was that the current non-js needed lots of love, but that we should focus on the topic and reply workflows (which are currently being looked on as part of this iteration [1]) Any functions that didn't fit into this, where the UX was suboptimal would be hidden, even if they were functional. The link to summarize for instance will take you to a page like this: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Topic:S15sspioi5wvqz… The page simply shows a textarea and doesn't really help you understand what you are doing. Likewise clicking edit title takes you to a page like so: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Topic:S15sspioi5wvqz… Displaying them again is pretty easy (Shahyar already has a patch [2]) but the UX love is much needed before doing so. [1] https://trello.com/c/fp2odUa3/531-g-1-mobile-no-js-make-reply-field-a-link-… [2] https://gerrit.wikimedia.org/r/153354