Fix potential form ID discrepancy between search form text input and button #3664
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.
In #3659 we modified the
search_form.html
template so the search text input can point to an arbitrary form. (This is useful on the paid registrar approval page, because there are two forms that submit data using different methods.)I missed one detail: if an arbitrary
form_id
is supplied, the search submission button needs to point to it as well. Otherwise, hitting Enter within the text input and clicking the submit button may produce unexpectedly different results.