You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good: If a HTML::Form::ListInput is created from a <select> tag, its ID attribute is taken from the id attribute of the <select> and the ids in the <option>s are ignored.
Less good: for radio buttons, there is no enclosing tag around the <input>s, and HTML::Form takes the ID attribute from the first <input> tag and applies it to the whole HTML::Form::ListInput object. I don't think that makes sense. It seems to me that an HTML::Form::ListInput from a set of radio button inputs should have no ID at all. If this IS intended behavior, then I think that's something that should be explained in the docs.
The text was updated successfully, but these errors were encountered:
petdance
changed the title
Radio buttons should not have ID attributes, but take the ID of the first <input> tag
Radio buttons should not have ID attributes, but they take the ID of the first <input> tag
Mar 14, 2024
Consider the following:
Results are:
This demonstrates that:
Good: If a HTML::Form::ListInput is created from a
<select>
tag, its ID attribute is taken from theid
attribute of the<select>
and theid
s in the<option>
s are ignored.Less good: for radio buttons, there is no enclosing tag around the
<input>
s, and HTML::Form takes the ID attribute from the first<input>
tag and applies it to the whole HTML::Form::ListInput object. I don't think that makes sense. It seems to me that an HTML::Form::ListInput from a set of radio button inputs should have no ID at all. If this IS intended behavior, then I think that's something that should be explained in the docs.The text was updated successfully, but these errors were encountered: