Page MenuHomePhabricator

en.wikinews Liquid Threads implementation has weird layout issue
Open, LowestPublic

Description

On English Wikinews (en.wikinews.org), we have Liquid Threads activated in a namespace called "Comments". This is to allow readers to post comments on articles. This complements the Talk namespace, which is labelled 'Collaboration' and is for the authors of the article to use much like a Wikipedia talk page.

On English Wikinews, the Liquid Threads extension is not being displayed correctly.

An example of a LiquidThreads thread on en.wn:

https://en.wikinews.org/wiki/Comments:%27Stop_being_so_damn_respectful%27_say_free_speech_supporters_in_London

Compare the lack of styling on the elements to a screenshot of how LiquidThreads is supposed to look:

https://www.mediawiki.org/wiki/File:LiquidThreads_sample_screenshot.jpg

All the options that should be tucked away in the "More" section are just layed out sequentially under the comment.

I've started a thread on en.wn's Water Cooler (Village Pump equivalent).

https://en.wikinews.org/wiki/Wikinews:Water_cooler/technical#Liquid_Threads


Version: unspecified
Severity: normal

Details

Reference
bz40501

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 1:10 AM
bzimport set Reference to bz40501.
bzimport added a subscriber: Unknown Object (MLST).

[ Moving to a plain LQT bug, as it doesn't seem to be related with the Wikinews site configuration. ]

All the options that should be tucked away in the "More" section are just layed
out sequentially under the comment.

Not visible to me... What browser are you using.


This is possibly my fault. Long long ago we wanted LQT to look a tad different and hence wikinews has some custom css for lqt in mediawiki:Common.css. Possibly there is some incompatibilities there.

Jdforrester-WMF lowered the priority of this task from Low to Lowest.Aug 4 2016, 11:34 PM
Jdforrester-WMF subscribed.

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.