Bug 334299 - edit function for comments
Summary: edit function for comments
Status: CONFIRMED
Alias: None
Product: bugs.kde.org
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist with 26 votes (vote)
Target Milestone: ---
Assignee: KDE sysadmins
URL:
Keywords:
: 329661 341271 349890 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-05-03 21:42 UTC by krichter
Modified: 2021-12-15 18:03 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description krichter 2014-05-03 21:42:52 UTC
Allow creator of a comment to edit her_his comment X minutes after they are submitted. This serves to avoid extra comments serving the correction of errors in the post which are found shortly after submitting.
This should implies to delay the notification of the CC list and notification of users commenting at the same time with.
Editing after other user read the post (like in a Q&A) shouldn't occur and should be prevented with the delay of the notification.
This depends on bugzilla bug https://bugzilla.mozilla.org/show_bug.cgi?id=540 getting fixed.

Reproducible: Always
Comment 1 Christoph Feck 2014-05-04 00:51:57 UTC
That sounds like a good compromise to what was discussed at bug 329661.

I love that Bugzilla bug. Makes me feel good that KDE isn't the only community which has open bugs that are older than mankind :)
Comment 2 Ben Cooksley 2014-05-12 06:07:34 UTC
*** Bug 329661 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2014-11-26 01:20:03 UTC
*** Bug 341271 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Feck 2015-07-04 21:41:37 UTC
*** Bug 349890 has been marked as a duplicate of this bug. ***
Comment 5 Philippe Cloutier 2019-07-17 20:56:29 UTC
I agree but think comments should always be editable. There should simply be a history of edits (if someone has read the previous versions, indeed).

This will apparently be solved in Bugzilla 6, which would probably release this year...