Use form.element.namedItem to track associated inputs.
#4103
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #4102. A couple tests are failing, but they were already failing when I first cloned the repo.
Before, it was required that all form elements be nested under the form. However, forms are allowed to have inputs located elsewhere as long as they use the
form="my-form-id"attribute.This changes it to use
form.elements.namedItem(name).form.elementsis already used inresetFormso this change is consistent with existing code.Note that radio/checkboxes with the same names will return a list, whereas
querySelectoronly returned the first result, so I'm only matching on the first element to match existing behavior. I'm not familiar enough with what exactlyincCycle/deletePrivateare doing, but I can update this to run those functions on all matching elements if needed.