-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pin floating-ui/react-dom
version
#48402
Conversation
Size Change: 0 B Total Size: 1.33 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can confirm that upgrading to version 1.3.0
introduced the issue, and pinning it to 1.0.0
restores it to the previous behavior.
Flaky tests detected in 4031dba. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4262046166
|
1d1e8e4
to
4031dba
Compare
I just cherry-picked this PR to the wp/6.2 branch to get it included in the next release: 15b60c2 |
@ciampo, @mirka, did you get a chance to track down what was causing this breaking change with the latest versions of This hotfix requires a manual Screenshot |
@Mamaduka Marco is away for the next two months, but looking into the trail, it's likely that this attempted upstream fix is messing with our custom workaround (#46845). The iframe issue in floating-ui is definitely still on our todo list, but I'm afraid we don't have an ETA yet 🙁 But thanks for letting us know about this hassle — it will bump up the priority 🙏 |
Thank you, @mirka 🙇 |
What?
Fixes: #48059
Fixes: #48398
Similar to: #48237
Why?
Core resolves different version
1.3.0
and it seems something has changed that causes these problems.Ideally we should update the version in GB and resolve the issues, but beta 4 is in a few days. So I think this
hotfix
for core it's an acceptable temporary solution.Testing Instructions
We'll need to do a packages update for 6.2 to verify it resolves the issues.