Let TextArea (SelectionField, calendars) have required, autofocus HTML5 attributes.

[nphilipp]

This lets developers set required on the widget, making it more
similar in look and field to other input fields.

[amol-]

As pointed out by testsuite,
this ended up adding an extra value= attribute which wasn't expected

AssertionError: Attributes do not match: value='6', value=None
xml1 <textarea  rows="6" cols="10" value="6" class="something">6</textarea>
 does not equal xml2
 <textarea class="something" rows="6" cols="10">6</textarea>

[moschlar]

Do you have a specific reason for this PR?

Because, conceptually, a textarea just isn't an input field (the naming there is analogous to the html tags).

[nphilipp]

The purpose of this was to be able to set required on the TextArea widget, so it gets rendered the similarly to other input fields, i.e. gets a red border if focused and the user hasn't entered anything yet.

I guess the shortcut I took was too short, so it's back to the drawing board. ;)

[nphilipp]

Skimming the HTML form fields documentation it seems as if required (and autofocus) could just as well go into FormField, but there's the conflicting(?) FormField.required property. What's the meaning of it? In many form field widgets it's shadowed by InputField.required (a Param) anyway.