wordpress-plugin

What problem does this address?

When reviewing #35361, I noticed there are no end to end tests for post locking.

What is your proposed solution?

It would be great to add end to end tests to cover this functionality. To lock a post in a e2e test it should be a simple matter of running await page.evaluate( () => wp.data.dispatch( 'core/editor' ).lockPostSaving( 'futurelock' ) );.

The

Many user have expressed how useful GraphQL Voyager has been as they work on sites powered by WPGraphQL.

It would be nice to let users use GraphQL Voyager within their WordPress dashboard alongside GraphiQL.

See: https://github.com/APIs-guru/graphql-voyager

Bug Description

On an AMP-first site I ran across the following amp-img:

<!--noscript-->
<amp-img height="1" width="1" alt="fbpx" src="https://www.facebook.com/tr?id=413752866132374&amp;ev=PageView&amp;noscript=1" class="amp-wp-enforced-sizes amp-wp-6a19fc1 i-amphtml-layout-intrinsic i-amphtml-layout-size-defined" layout="intrinsic" data-amp-

Feature Description

Inspired by this tweet from @Siddhart I was considering whether we could do something similar when selecting font color or text background color where we highlight recommended colors for a proper text c

Describe the bug:

Certain components have defined propTypes that allow for greater engineering confidence when developing. Efforts should be made to properly define propTypes across the CoBlocks repository.

Expected behavior:

Expect that propTypes are known and defined across CoBlocks.

Existing defined

Is your feature request related to a problem? Please describe.
SEO is very important to my client and having full control over what's in the element is ideal.

Describe the solution you'd like
The Lazy Loaded Scripts, Critical CSS, Combined CSS, and Used CSS tags were all getting placed into the element by replacing the closing </title> and closing tags.

What