TYPO3.Fluid

Try validating against HTML 5.

Besides: If you're using the markup in your example you'll notice that it doesn't work as expected – clicking the label will not select the checkbox (presumably because the browser implicitly associates the label to the first <input> element it contains in this ambiguous situation). So it's poor usability which is how I found this problem to begin with. In fact, I'm surprised doing this was valid in HTML 4.

Sven-S. Porst wrote:

Try validating against HTML 5.
[...] it doesn't work as expected [...]

Good point(s) ;)
I'm not sure how to solve this though.. I don't think, that the form view helper should output the label, because then you'd have to be able to specify some kind of template for the exact output.
Maybe a solution would be to make the hidden field optional (<f:form.checkbox createHiddenField="false" />) so that you'd be able to render it yourself. To avoid a lot of duplicate template code, you could put this into a partial:

1<li>
2    <f:form.hidden property="{property}" value="" />
3    <label>
4        {label}
5        <f:form.checkbox property="{property}" createHiddenField="false" />
6    </label>
7</li>

and use it like:

1<f:render partial="Checkbox" arguments="{property: 'foo', label: 'Foo'} />

what do you think?

The createHiddenField approach would certainly help with my specific problem.

On the other hand, adding an extra paramter would add addional complexity to the view helper's interface, so I'm not sure this is a really good solution if the templating is meant to be easy to use.

If one needs those hidden fields, a more elegant solution would be if the hidden fields were not inserted directly by the form field's view helper but collected by the containing form view helper and then inserted at the beginning of the form.

The referrers are inserted at the beginning of the form. So the setup seems to be just right.

Sorry for the delay on this one. I take care of implementing this for 1.1!