Project

General

Profile

Actions

Feature #22326

closed

Confirmation dialog missing when unsaved changes are about to be lost

Added by Xavier Perseguers about 14 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
Start date:
2010-03-25
Due date:
% Done:

0%

Estimated time:
PHP Version:
5.3
Tags:
Complexity:
easy
Sprint Focus:

Description

This is a feedback from OpenExpo in Bern/Switzerland.

Editors are often disturbed by the lack of confirmation dialog whenever they have some unsaved text being edited and they incidentally (or not) click on some left menu link.

How to reproduce:

- Create a new text element
- Write some text, do not save it
- Click on some link in left menu (e.g., "Show", or "Ext Manager")

You are not asked whether you want to save your work. This would be an awesome enhancement in term of usability.

(issue imported from #M13915)


Related issues 1 (0 open1 closed)

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

Actions
Actions #1

Updated by Chris topher almost 14 years ago

Such a dialog could be added at several places:
When content has been changed and not saved in
- a page
- page content
- in a BE user record
- in a FE user record
- in user settings

On the other hand adding this at too many places would force the user to press a button, also if he intentionally wanted to discard his changes by going away. I don't think that forcing users to (in such cases) always press a button would be good.

Instead an option to enable or disable such behaviour would be fine; maybe called "Enable childrens' mode". (Don't take the naming to serious. ;-) )

Actions #2

Updated by Gone With the Wind almost 12 years ago

  • Target version deleted (0)

Any chance to discuss this topic again? There should be ways to offer such a feature, at the same time turn it off globally in the user setting (e.g). Let's not forget that most people are on windows where you - like it or not - get trained in alert box orgies, and not all of the are bad. My experience is that more people expect such a behaviour than not.

Actions #3

Updated by Helmut Hummel almost 12 years ago

  • Category set to Backend User Interface
  • Status changed from New to Accepted
  • Target version set to 6.0.0-alpha3
  • TYPO3 Version set to 6.0
  • PHP Version changed from 4.3 to 5.3
  • Complexity set to medium

I'd like to see this feature in 6.0

Let's see what I can do.

Actions #5

Updated by Helmut Hummel over 11 years ago

  • Target version changed from 6.0.0-alpha3 to 6.0.1
Actions #6

Updated by Mathias Schreiber over 9 years ago

  • Target version changed from 6.0.1 to 7.4 (Backend)
  • Complexity changed from medium to easy

Should be easy with the "dirty" marker we already have.
Modal box maybe

Actions #7

Updated by Susanne Moog almost 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #8

Updated by Benni Mack over 8 years ago

  • Target version changed from 7.5 to 7 LTS
Actions #9

Updated by Mathias Schreiber over 8 years ago

  • Status changed from Accepted to Resolved

;-)

Actions #10

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF