Project

General

Profile

Actions

Feature #15138

closed

Cancel buttons should ask for confirmation if there are unsaved changes

Added by Oliver Klee about 19 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2005-10-20
Due date:
% Done:

0%

Estimated time:
PHP Version:
4.3
Tags:
Complexity:
Sprint Focus:

Description

If you edit e.g. a template and press Cancel/Close, all changes after the last save are lost. The editor should warn and ask for confirmation if the user has changed the editor contents. This can prevent dataloss.

This could look like this:

There are unsaved changes. Do you want to discard them?

[Save] [Discard] [Cancel]

The "Cancel" button then will return to the editor.

This is related to issue 1701.
(issue imported from #M1702)


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #15137: Rename Cancel buttons to CloseClosedOliver Hader2005-10-20

Actions
Is duplicate of TYPO3 Core - Feature #22326: Confirmation dialog missing when unsaved changes are about to be lostClosed2010-03-25

Actions
Actions #1

Updated by Sebastian Kurfuerst about 19 years ago

We cannot currently fix this during "zap the gremlins", but a patch for this is very welcome.
Greets, Sebastian

Actions #2

Updated by Chris topher over 14 years ago

I am strongly against such a feature.

When the user pressed abort, he actively made a decision. In almost all cases he will have done so intentionally. So asking him if he was really sure, is a change to the worse.
Imagine a user typing text in the RTE. We also don't ask him "Did you really want to press "a"?" That kind of behaviour is annoying rather than helpful.

If you want to prevent unsaved changes from being lost, please have a look at #22326, because there we cannot be that sure that the user acted intentionally.

Actions #3

Updated by Oliver Klee over 14 years ago

I think we can mark this bug as a duplicate of #22326 (or drop it ... I don't feel very passionate about this one).

Actions #4

Updated by Chris topher over 14 years ago

Resolved as duplicate of #22326.

Actions #5

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF