Form::setDisabled clear value

h4kuna

Hi, I created form with disabled input and with default value.

<?php
$form = new Nette\Forms\Form;
$form->addText('name')
	->setDefaultValue('Milan')
	->setDisabled();

echo $form;
?>

Output:

<input name="name" type="text" disabled="disabled" />

But I want

<input name="name" type="text" disabled="disabled" value="Milan" />

When I change order, because setDisabled() clear value. Why if exists flag omitted?

This get right output.

<?php
$form = new Nette\Forms\Form;
$form->addText('name')
	->setDisabled()
	->setDefaultValue('Milan');

echo $form;
?>

Michal Vyšinský

Hi,
IMO it is not bug. I think it is for security reason. When someone change HTML in developer tools and remove disabled + add value POST will send that value. Thanks to clearing value of the field the value will be removed from POSTed data.

h4kuna

I understand, this case works fine like protection for developer's tools and this does what i want.

<?php
$form = new Nette\Forms\Form;
$form->addText('name', 'Name')
	->setDisabled() // try this call move end
	->setDefaultValue('Milan');

$form->addSubmit('send');

if($form->isSubmitted()) {
	dump($form->getValues(), $_POST);
	exit;
}

echo $form;
?>

I describe render input type text with attribute disabled not if you send data.

h4kuna

Let's try run this code:

<?php
$form = new Nette\Forms\Form;
$form->addText('name')
    ->setDefaultValue('Milan')
    ->setDisabled();

echo $form;
// another form
$form2 = new Nette\Forms\Form;
$form2->addText('name')
    ->setDisabled()
    ->setDefaultValue('Milan');

echo $form2;
?>

$form and $form2 haven't same output.

Michal Vyšinský

Sure it does not. First form calls ‘setDisabled’ after setDefaultValue so it will clear its value. Second solution is ok. I do not see a bug in this – the behaviour is logically correct. (Also trying to fix it [remove clearance of the value] would be BC break)

h4kuna

In Nette 2.0.6 $form and $form2 have same output. After update any forms not rendered correctly.

Forms are working fine.

David Grudl

Disabled controls are simply problematic.

There are a lot of quirks (see this), so current behavior is not ideal, but the best one.