Page MenuHomePhabricator

Fix paging for LiquidThreads discussion pages
Open, LowestPublic

Description

Big old icons, no numbering, nothing like that.

Needs sorting out.


Version: unspecified
Severity: enhancement

Details

Reference
bz19975

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 10:41 PM
bzimport set Reference to bz19975.
bzimport added a subscriber: Unknown Object (MLST).

Sticking Parul and Trevor from the usability initiative on CC, so we can get some more input here.

Totally agree. How about replacing them with these: http://commons.wikimedia.org/wiki/User:DieBuche/Lqt icons?

They are the same style as other vector buttons (taken from GNOME Desktop icons 2.20/Tango).
Additionally the buttons should get {text-decoration:none} to get rid of the weird lines behind the icons

Jorm added a comment.Sep 10 2010, 2:17 AM

Infinite scrolling FTW.

Re-opening this for now.

Whether or not JavaScript-enabled infinite scrolling is eventually implemented, people not using JavaScript need to have a usable interface. This is a core design principle in MediaWiki development.

I can't really speak to how "usable" the current paging system is, but I can say that there will be a percentage of users who will either intentionally disable all JavaScript when using LiquidThreads or who will intentionally disable the infinite scrolling feature due to the inevitable performance issues that accompany such features. In these cases, the paging interface must be acceptable.

(In reply to comment #4)

Infinite scrolling FTW.

adding 'javascript' keyword then

Jorm removed a subscriber: Jorm.Dec 26 2015, 7:25 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 26 2015, 7:25 PM
Jdforrester-WMF lowered the priority of this task from Low to Lowest.Aug 4 2016, 11:36 PM
Jdforrester-WMF added a subscriber: Jdforrester-WMF.

LiquidThreads has been replaced by StructuredDiscussions on all Wikimedia production wikis (except one, which will be done soon). It is no longer under active development or maintenance, so I'm re-classifying all open LQT tasks as "Lowest" priority.