Project

General

Profile

Actions

Bug #15137

closed

Rename Cancel buttons to Close

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

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

0%

Estimated time:
TYPO3 Version:
3.8
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

This is a usability issue: Most Cancel buttons in the back end, e.g. in the template editor, actually don't cancel the current action (saved changed will stay), but just close the editor.

So the Cancel buttons should be renamed to Close.

(issue imported from #M1701)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #15138: Cancel buttons should ask for confirmation if there are unsaved changesClosedChris topher2005-10-20

Actions
Actions #1

Updated by Sebastian Kurfuerst about 19 years ago

I am not sure if "close" is better. I think that, because the button "save" exists, the user would assume that the button "close" saves the document and closes afterwards. In my opinion, "cancel" is a more meaningful description for this action - cancelling what the user did.
Greets, Sebastian

Actions #2

Updated by Oliver Klee about 19 years ago

Um, if you think that this need discussion (it obviously does), please don't just close the bug report. This doesn't help in getting this usability problem solved.

BTW, this is related to 0001702, which is about a message box if there are unsaved changes.

Actions #3

Updated by Oliver Klee almost 19 years ago

This most annoys me when I have e.g. edited (and saved) a template and just want to close the editor, not cancel any changes.

Actions #4

Updated by Sebastian Kurfuerst almost 19 years ago

Hi,
I agree with you what concerns this button, but it would be really great to hear some other's opinions as well.
Greets, Sebastian

Actions #5

Updated by Stefano Cecere almost 19 years ago

what about "exit" ?

Actions #6

Updated by Oliver Hader about 16 years ago

Since TYPO3 4.2 and the "Cleaner Backend" project most of these issues were solved (e.g. on editing content elements or template records, etc.)

Actions

Also available in: Atom PDF