Size Change: -19 B (0%)

Total Size: 1.21 MB

_{compressed-size-action}

@ntsekouras thanks for the heads-up about the *.native.js changes. I smoke tested Media & Text, Columns, Buttons and Cover on mobile and everything looks OK 👍. The changes affecting native files appear to be only due to templateInsertUpdatesSelection previously defaulting to true and now defaulting to false.

It looks like this PR needs to be rebased.

I also marked it as needing a short dev note for WordPress 5.7 release. Can you compile something upfront so the process is more streamlined?

Dev Note for this change. (thank you @gziolo for the intro)

Inner Blocks API Changes

We noticed that the majority of block authors prefer to keep the focus on the parent block upon insertion in the editor rather than move it to one of the child blocks. Prior to the changes introduced the default behavior was the latter, so we decided to change it to follow the more popular choice that is going to simplify API usage. To accomplish that we had to change the definition of the following parts of API:

• InnerBlock component
• useInnerBlocksProps hook
• replaceInnerBlocks action

InnerBlock component and useInnerBlocksProps hook

Both handle the focus on the blocks with templateInsertUpdatesSelection property. If you want to keep the focus on the parent you can omit this property.

If you want to move the focus to the first child block you have to set this property to true. Examples:

<InnerBlocks template={ [ [ 'core/heading' ] ] }  templateInsertUpdatesSelection/>

const innerBlocksProps = useInnerBlocksProps(
	{       className: 'wp-block-cover__inner-container'       },
	{
		template: [ [ 'core/heading' ] ],
		templateInsertUpdatesSelection: true,
	}
);

replaceInnerBlocks action

Reference: https://developer.wordpress.org/block-editor/data/data-core-block-editor/#replaceInnerBlocks

This action handles focus with the third argument updateSelection. If you want to keep the focus on the parent you can skip this argument when calling replaceInnerBlocks.

If you want to move the focus to the first child block you have to pass this argument with true value. Examples:

replaceInnerBlocks( rootClientId, blocks, true )

@ntsekouras, how do you feel about using the following intro to this dev note that explains the reasoning behind these changes:

Inner Blocks API Changes

We noticed that the majority of block authors prefer to keep the focus on the parent block upon insertion in the editor rather than move it to one of the child blocks. Prior to the changes introduced the default behavior was the latter, so we decided to change it to follow the more popular choice that is going to simplify API usage. To accomplish that we had to change the definition of the following parts of API:

• InnerBlock component
• useInnerBlocksProps hook
• replaceInnerBlocks action