fix: Trigger ongot-/onlostpointercapture when calling got-/lostpointercapture #786
+17
−21
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:
Calling
fireEvent.gotPointerCapture
orfireEvent.lostPointerCapture
should trigger their corresponding React event listeners.Why:
Reveals issues with
gotpointercapture
andlostpointerapture
How:
@testing-library/dom
to version including fix(events): got-/lostpointercapture bubble dom-testing-library#767Checklist:
[ ] Documentation added to thedocs site
[ ] Typescript definitions updated