fix: mock brower event about issues 1327 #1328
Draft
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.
fix #1327
this pr is about mock brower event, it is a possible solutions to the #1327) issues
What:
This PR adds two new lifecycle methods,
before
andcond
, developers only need to control these two lifecycles to simulate most browser behaviors.. on top of the existing ones to simulate browser events. This is just a draft; please do not merge.Why:
The events in dom-testing-library are encapsulated based on the native Event class. However, when there are conflicts between this Event and native DOM events, it may not fully replicate the behavior.
How:
Checklist:
docs site
before this pr, it will trigger
dragstar
anddragover
event ,it is error because dragstart is prevent,it should only triggerdragstart
eventafter this pr ,when i test this case ,it 'll be as expect