Add force
argument to triggerEvent
#1521
Open
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.
I believe
triggerEvent
is too restrictive if it forbids all events on a form control with thedisabled
attribute. While the specification only mentions "click events" and MDN refers to "browsing events," all browsers currently allow mouse tracking events, such asmouseenter
andmouseleave
, to trigger on disabled controls. Additionally, there are events unrelated to user interaction, liketransitionend
andanimationend
.Beyond known events, there's also the case of
CustomEvent
, which is entirely valid in browsers but is currently blocked bytriggerEvent
.Maintaining a comprehensive list of forbidden or allowed events might not be practical or sustainable. However, I suggest providing testers with an option to trigger events on disabled elements if necessary.
This PR allows to bypass the availability check on a
disabled
form control using theforce
argument.