Preventing default action when pressing Enter key to add custom fields in Settings - Fixes #1395 #1417
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.
What kind of change does this PR introduce?
Bugfix
Issue Number:
Fixes #1395
Did you add tests for your changes?
Yes
Snapshots/Videos:
Screencast.from.2024-01-10.23-25-28.webm
If relevant, did you update the documentation?
No, No documentation changes were needed
Summary
This pull request addresses an issue where an error was triggered when clicking "Enter" instead of the submit button for adding new custom fields in the settings page. The root cause was that the form was being submitted when pressing "Enter," resulting in unexpected behavior. To fix this, I added a preventDefault action to the form submission and then called the handleSave function.
Does this PR introduce a breaking change?
No, this PR does not introduce any breaking changes.
Other information
[x] I've tested this fix thoroughly on various browsers to ensure compatibility.
[x] The code follows the coding standards and guidelines outlined in the contributing guide.
[x] This change has been made against the develop branch.
Have you read the contributing guide?
Yes