Project

General

Profile

Actions

Feature #57383

closed

Accidental doubleclick on save button creates two records

Added by Florian Seirer over 10 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-03-27
Due date:
% Done:

0%

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

Description

If I create a new record (doesn't matter which type) in the list module, and doubleclick the save button to save the records for the first time (!), two records are created. This happens for each click I can do before the backend finishes reloading the form.

So, 5 clicks in rapid succession mean 5 records.

Bug? Feature? Or just "Thou shalt not doubleclick in a browser"?

Actions #1

Updated by Florian Seirer over 10 years ago

It doesn't even have to be rapid clicking. A slow backend can cause the same behaviour.

An idea on how to fix this could be to deactivate the save button through an onclick-event until the form is reloaded.

Actions #2

Updated by Philipp Gampe over 10 years ago

  • Status changed from New to Needs Feedback

I'd say this is more of a feature.

Actions #3

Updated by Markus Klein over 10 years ago

  • Status changed from Needs Feedback to New

I don't like the suggestion of disabling a button. What if you're on an unstable connection an the connection breaks while initiating the first request. The user will loose all entered data, as the save button is now disabled.

Much better way is to use a form token to detect multiple submits.
Maybe Helmut can say some words here.

Actions #4

Updated by Mathias Schreiber almost 10 years ago

  • Tracker changed from Bug to Feature
  • Target version set to 7 LTS
Actions #5

Updated by Benni Mack about 9 years ago

  • Target version deleted (7 LTS)
Actions #6

Updated by Riccardo De Contardi about 9 years ago

  • Status changed from New to Closed

As far as i can see on version 7.6 it is solved , so I close this.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF