It was built with non-JS in mind. What you are referring to, however, is the flash of pre-JS styling. flow-menu should look fine in no-JS mode, because it's implemented with CSS only. Only older browsers require JS to make it work. However, I made some errors during the implementation, and exposed the more ugly version initially. This is something to be rectified.
--Shahyar On Fri, Aug 29, 2014 at 5:32 PM, Jon Robson <[email protected]> wrote: > I would not object to restoring permalink but I worry the list might > look rather empty without it. I'd rather we put effort into improving > UX. I doubt that would be too much work, but it needs design input and > prioritisation. > > > On Fri, Aug 29, 2014 at 8:25 PM, S Page <[email protected]> wrote: > > On Wed, Aug 27, 2014 at 2:41 PM, Jon Robson <[email protected]> > wrote: > >> > >> 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) > >> > >> ... > >> > >> Any functions that didn't fit into this, where the UX was suboptimal > >> would be hidden, even if they were functional. > > > > > > Thanks for the explanation. But e.g. the Permalink action is perfectly > > functional in no-JS. Are y'all going to revive that one action menu > item, > > or wait for everything in the menu to get to the same quality level as > no-JS > > reply before enabling it? > > > > -- > > =S Page Features engineer > > > > _______________________________________________ > > EE mailing list > > [email protected] > > https://lists.wikimedia.org/mailman/listinfo/ee > > > > _______________________________________________ > EE mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/ee >
_______________________________________________ EE mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/ee
