-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Fix intermittent RichText e2e test failure #20457
Conversation
Size Change: 0 B Total Size: 865 kB ℹ️ 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 was looking into this right now! Thanks for solving it! 😊
Did this start happening very recently? |
@ellatrix I only saw it today. |
It seems that it started on #19242, specifically on this line:
The old implementation was using |
@diegohaz Seems like using |
We may lose some performance benefit. But, yeah! Using |
I updated, let's see what travis says. |
@diegohaz Looks like there's a JS unit test failure now, would you be able to help? |
Storyshots use react-test-renderer underneath, which doesn't support ReactDOM.createPortal
It seems that storyshots is trying to create portal now that it's sync. Storyshots uses react-test-renderer underneath, which doesn't support portals. Mocking |
SlotFill uses ReactDOM.createPortal, which is not supported by Storyshots and react-test-renderer
Should be fixed now! |
Thanks :) I'm questioning Storyshots more and more. I haven't seen any value so far. |
It seems like there might a be a very small delay between the mouse moving and the block toolbar being shown causing a test failure.
This PR fixes the issue by waiting for the toolbar to show before proceeding.