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
In some pages, that probably isn't technically proper HTML, the form tag can be prematurely closed and not have any children. In this case, there will still be input-elements linked to the form, and the form will submit just fine. However, using querySelectorAll on the form will always result in an empty result-set, since the form has no children.
It would be interesting to investigate an approach where we look at form.elements (which will hold all the inputs linked to the form) instead of using querySelectorAll on the form.
Looking further into this, I think that sites such as moje.axa.cz (mentioned recently) have a form and elements but they're not linked - it's a good example that we need to remove our dependence on <form>s altogether. I'll close this in favour of a new issue: #33
In some pages, that probably isn't technically proper HTML, the form tag can be prematurely closed and not have any children. In this case, there will still be
input
-elements linked to the form, and the form will submit just fine. However, usingquerySelectorAll
on the form will always result in an empty result-set, since the form has no children.It would be interesting to investigate an approach where we look at
form.elements
(which will hold all the inputs linked to the form) instead of usingquerySelectorAll
on the form.example site: http://www.aavtrain.com/create_user.asp
The text was updated successfully, but these errors were encountered: