Form submission: Identify pressed submit button associated through form attribute#5190
Merged
Merged
Conversation
22774ef to
e5f0abf
Compare
nilmerg
requested changes
Nov 4, 2024
823dd53 to
8f277bf
Compare
8f277bf to
ee57aee
Compare
nilmerg
approved these changes
Nov 4, 2024
nilmerg
added a commit
to Icinga/icinga-notifications-web
that referenced
this pull request
Sep 1, 2025
Use a single form for event rule configuration. Blocked by Icinga/icingaweb2#5190
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue
When there are multiple submit buttons outside the form which are associated with it as shown below, the form fails to correctly identify the pressed submit button.
Solution
In case the button is undefined upon submit event, get the pressed submit button using the submitter property found on the
SubmitEventinterface.