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
It's been a long time since I did any html, but I remember being able to use names such as foo[0].bar or foo[] as input field names, so that a web framework could reconstruct a nested structure from query/form parameters. It seems this is not currently supported, and the attribute is defined as being of type ID.
Using such a name leads to a runtime panic such as
ERROR: <input name="foobar[]"> failed to parse attribute value: ID can only contain alphanumerics, dash, dot and underscore
The whatwg html spec does not seem to restrict the contents of the name attribute:
Other than isindex, any non-empty value for name is allowed
The text was updated successfully, but these errors were encountered:
This is true, yeah. You'd especially use this in the context of complex web forms that are generated either server-side or by some client-side framework (especially the former is important for axohtml's usage). I think we can relax these restrictions.
It's been a long time since I did any html, but I remember being able to use names such as
foo[0].bar
orfoo[]
as input field names, so that a web framework could reconstruct a nested structure from query/form parameters. It seems this is not currently supported, and the attribute is defined as being of typeID
.Using such a name leads to a runtime panic such as
The whatwg html spec does not seem to restrict the contents of the
name
attribute:The text was updated successfully, but these errors were encountered: