[TYPO3-project-4-3] admin panel - why are the form options duplicated?

Jigal van Hemert jigal at xs4all.nl
Mon Jul 6 16:52:37 CEST 2009


Hi Masi,

Martin Kutschker wrote:
> This would no be a problem if the code would check the expected form
> fields and not the ones sent. So any field not present means "not set".

With more complicated forms and interaction on the client side (AJAX, 
DOM manipulation) it can become rather difficult for the script that 
handles the submitted data to know what to expect.

The behaviour of checkboxes is rather odd; they can be checked, not 
checked or disabled. In the latter two cases the should not be sent to 
the server (they are not 'successful'). In case a checkbox is cleared 
the value should be unset, but in the case that a checkbox is disabled 
(e.g. by a piece of Javascript) the value should not be changed. How can 
you tell the difference?

Hidden fields can be used to tell more about the fields that are 
supposed to be present; quite useful.

Regards,

-- 
Jigal van Hemert.


More information about the TYPO3-project-4-3 mailing list