Set chromeWebSecurity config value to false by default
#34
Conversation
This file contains 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.
Description of the Change
Due to changes in WordPress 6.3 that tries to load the block editor in an iframe by default, setting
chromeWebSecuritytofalsehelps avoid errors interacting with that iframe.In addition, tests were failing due to some changes needed for the latest version of
wp-env. This has been duplicated from #35 just so tests will pass.Alternate Designs
None
Possible Drawbacks
I'm not aware of any issues with setting this to
falseVerification Process
If desired, check out the branch and run the setup process
Checklist:
Changelog Entry
Credits
Props @dkotter