Topic on Talk:Talk pages project/Replying/Flow

Call for unexpected behavior

4
PPelberg (WMF) (talkcontribs)

When posting a comment using the new Replying workflow, have you noticed other parts of the talk page being unintentionally and/or unexpectedly affected?

The two instances we are aware of right now are the following:

  • T242466: Why does posting a new comment delete `</span>` from a previous one?
  • T246481: Prevent page corruption in DiscussionTools caused by broken and incomplete table syntax

If you do happen on a case that looks like content corruption, the team would value you sharing it in this thread.


Note: to help us investigate the issue more quickly, we would appreciate you following the "Reporting instructions" below.

PPelberg (WMF) (talkcontribs)

Reporting instructions

If you come across a case where posting a reply using the Replying tool unexpectedly affects other parts of the talk page, we would value you sharing it here, along with the details listed below:

  1. A link to the diff showing the behavior you experienced/noticed
  2. The content of the comment you posted using the Reply tool
  3. What you expected to happen after posting said comment
  4. What actually happened after posting said comment
  5. When relevant, links to existing talk pages where the content you are trying to post is being used
Alsee (talkcontribs)

One of the lessons of Flow was that people learned to stop filing bug reports. The design was fundamentally flawed, the Foundation refused to fix the design, working on the bugs would do nothing to solve the design. Further bug reports only made things worse when the Foundation flushed even more precious dev-time down the toilet on things-that-shouldn't-be-fixed.

I continue to find severe problems in the current product - in particular content which causes it to fail and spit out an error. The issues would vanish if you fixed the design. If you refuse to fix the product, then I expect the community will not allow it to be deployed. Either way, it makes no sense to file further bug reports.

Aron Manning (talkcontribs)
Reply to "Call for unexpected behavior"