Page MenuHomePhabricator

Posting a reply to a thread does not display post after hitting save if number of replies is > number of replies to show in pref
Open, LowestPublic

Description

I think this is a 1.19 regression (or regression in whatever version of lqt was deployed when wmf wikis hit 1.19)

This was observed on mediawiki.org

Steps to reproduce:
*Go to special:newmessages (I assume you have new messages)
*Reply to some thread
*Hit save to your reply

Expected behaviour:

The reply is parsed and displayed under the message

Actual behaviour:

The reply window disappears, and there is no indication that your reply was successfully posted.


Version: unspecified
Severity: normal
URL: https://www.mediawiki.org/wiki/Thread:User_talk:Werdna/LiquidThreads_is_awesome

Details

Reference
bz34765

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 12:18 AM
bzimport set Reference to bz34765.
bzimport added a subscriber: Unknown Object (MLST).

Does this happen only on Special:Newmessages, or does it also happen directly on a threaded view such as here:

https://www.mediawiki.org/wiki/LQT_test

?

Either way, appears to work for me in Firefox 10.0.2 / Ubuntu 11.10.

Tested, it didn't happen on LQT_test, so only on special:newmessages.

My browser is a tad old, but things definitly used to work fine.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20110302 Iceweasel/3.5.16 (like Firefox/3.5.16)

Works for me on Special:NewMessages with Iceweasel 3.5.16 on a fresh Debian 6.0 install.

OK, I think this is only triggered if the number of replies goes past what is in my preferences for max number of replies to show (Which kind of makes sense I suppose logically, but is unintuitive - especially because one has already expanded the thread at this point, so would expect the new reply to be shown. At the very least, some sort of indicator of success should be shown)

To see if this is a 1.19 regression, you can use https://hu.wikipedia.org/wiki/Szerkeszt%C5%91vita:MarkAHershberger -- my test LQT setup for 1.18. But test quickly since we may update any time now.

(In reply to comment #5)

To see if this is a 1.19 regression, you can use
https://hu.wikipedia.org/wiki/Szerkeszt%C5%91vita:MarkAHershberger -- my test
LQT setup for 1.18. But test quickly since we may update any time now.

My apologies, appears not to be a regression - I just happened to hit the bug around time 1.19 was deployed.

Have seen this quite a while in twn net.

(In reply to comment #4)

OK, I think this is only triggered if the number of replies goes past what is
in my preferences for max number of replies to show (Which kind of makes
sense
I suppose logically, but is unintuitive - especially because one has already
expanded the thread at this point, so would expect the new reply to be shown.
At the very least, some sort of indicator of success should be shown)

Still happens: https://test2.wikipedia.org/wiki/User_talk:Qgil#Testing_Bug_34765_50

And I agree. This is nasty from a usability point of view.

  • Bug 47051 has been marked as a duplicate of this bug. ***
Jdforrester-WMF lowered the priority of this task from Medium to Lowest.Aug 4 2016, 11:34 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.