Added standard composedPath method #6426 #6450
Merged
Conversation
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
added themeMode story in storbook
updated themeMode storybook removed unwanted comment from Grommet.js
ericsoderberghp
approved these changes
Oct 25, 2022
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.
Fixed the non-standard
event.pathtoevent.composedPath- #6426What does this PR do?
Use of
event.pathwas is not supported on browsers like FireFox, a simple fix here was to use theevent.composedPath()methodWhere should the reviewer start?
Line 262 in DropContainer.js
What testing has been done on this PR?
How should this be manually tested?
Do Jest tests follow these best practices?
screenis used for querying.userEventis used in place offireEvent.asFragment()is used for snapshot testing.Any background context you want to provide?
What are the relevant issues?
#6426
Screenshots (if appropriate)
Do the grommet docs need to be updated?
Up to the maintainers to decide.
Should this PR be mentioned in the release notes?
Is this change backwards compatible or is it a breaking change?