@Sidsector9 @iamdharmesh is the WP latest failure a concern here or good to merge this in?

The WP Latest test failures are intermittent both locally and in the GH Actions. Running in the browser I am seeing some issues with the rendering of the editors iframe but I am unsure if that is happening in the GH actions too.

In the most recent push, the first run fails with Create Post > Should be able to create Page

In the second run both Create Post > Should be able to create Page and Create Post > Should be able to create Draft Page fail.

Similar happening elsewhere.

@peterwilsoncc I've taken a look at this and whilst I can't replicate the error locally, I do see the following in the artifacts from the latest GH Actions failure:

This seems to me that something is causing the editor to fall over. Is there anyway to get more information about general JS errors rather than Cypress specific errors? That will likely give us more insight into what's going on under the hood.

I've been able to reproduce locally using the electron browser rather than Chrome but not seeing any hints in the console when running cypress open.

Thanks @peterwilsoncc! Running in Electron I was able to reproduce that error. If I enable SCRIPT_DEBUG, I can see the following error.

This error points at this line:

https://github.com/WordPress/gutenberg/blob/trunk/packages/block-library/src/image/use-client-width.js#L20

Interestingly, if you log out ref.current.ownerDocument, the defaultView property is null:

Yet if you log out the extracted defaultView const, you get this:

but notice how removeEventListener() isn't a function defined on that object 🤔

I'm assuming this is a bug in Electron browser windows, but I'm not sure where that leaves us or this test.

@darylldoyle Thank you! That's a great help.

In 9fffc47 I've switched the GitHub actions to use Chrome and will run the test suite a few times to see if it ends up less flaky.

It's probably a good thing to do as it better represents what the end user is running and that's the purpose of the test suite.

cc: @iamdharmesh we've switched back to Chrome 😄