New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 6984 link

Starred by 6 users

Issue metadata

Status: Released
Last visit > 30 days ago
Closed: Nov 20

Sign in to add a comment

"Discard" button on review comments is destructive, doesn't have a confirmation prompt and no undo

Project Member Reported by, Aug 9 2017

Issue description

Affected Version:

What steps will reproduce the problem?
1. Write some comment on a CL
2. Try to hit "Save", miss, and hit "Discard" accidentally

What is the expected output?

I should be able to get my carefully written comment back.

What do you see instead?

The comment contents are destroyed, I need to retype everything. For longer comments, that can cost several minutes.

Please provide any additional information below.

Project Member

Comment 1 by, Sep 5 2017

Labels: Triaged-Yes Hotlist-Comments Milestone-Chromium-Afterglow Priority-2
Project Member

Comment 2 by, Oct 18 2017

Status: Started (was: New)
Project Member

Comment 3 by, Oct 18 2017

Status: ChangeUnderReview (was: Started)
Project Member

Comment 4 by, Oct 19 2017

Status: Submitted (was: ChangeUnderReview)
Project Member

Comment 5 by, Oct 20 2017

Just tested this with the latest 2.15 build. Works very well, thanks!

Maybe worth noting that it also displays the confirmation dialog after initially saving the comment. :-)
Project Member

Comment 6 by, Oct 25 2017

 Issue 7548  has been merged into this issue.
Project Member

Comment 7 by, Oct 25 2017

Status: Released (was: Submitted)
Project Member

Comment 8 by, Oct 26 2017

Sorry to be a downer, but I strongly dislike the current confirmation dialog. I frequently discard comments as I'm developing a code review, and having to move my mouse far away from the discard button is quite annoying. For me personally, the ratio of intentionally to unintentionally discarded drafts is high.

I completely sympathize with the original problem, however, that discard is unnecessarily destructive. Rather than a confirmation dialog, I would prefer some kind of undo mechanism, such as:
* A toast with an undo button.
* A short inline thing with an undo button
* Prepopulate a new comment box with the old text if you recreate a comment on the same line.
Project Member

Comment 9 by, Oct 26 2017

Status: Accepted (was: Released)
Project Member

Comment 10 by, Dec 1 2017

The plan is to replace the confirmation with some kind of unobtrusive undo toast.
Project Member

Comment 11 by, Nov 20

Status: Released (was: Accepted)
Labels: FixedIn-2.16

Sign in to add a comment