-
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
Dev Notes for WP 5.6 #26108
Comments
Pretty sure this was done for WordPress 5.5. It shouldn't be needed for the WordPress 5.6 release? |
I can confirm it was released in WP 5.5, related Dev Note is here: https://make.wordpress.org/core/2020/07/30/block-api-updates-in-5-5/. |
I think the dev notes for 5.5 here were published but the label from the PRs were not removed. |
Dev note for Fix: Media Text: Always show images on top on mobile - #24468. Media & Text blocks on mobile now always show media on top.Previously, if the stack on mobile behavior was not disabled, and media had the option to appear on the left (the default), on mobile, the media appeared on top and the text on the bottom. If media had the option to appear on the right on mobile when stacked media would appear at the bottom and text on top. |
Dev note for Convert all px values in front-facing styles to relative (em) units - #24523 Default block styles now use font-size-relative values instead of absolute pixel values.Previously, blocks were using hardcoded pixel values for all their sizing properties (paddings, margins, font-sizes etc). |
Dev notes for Make accessible toolbar stable and deprecate old usage - #23316 Toolbar shouldn't be used within other toolbarsTo better reflect its semantics, the Before <BlockControls>
<Toolbar>
<ToolbarButton />
</Toolbar>
</BlockControls> After <BlockControls>
<ToolbarGroup>
<ToolbarButton />
</ToolbarGroup>
</BlockControls> Block toolbars now require controls to be ToolbarButton or ToolbarItem elementsRendering native Before <BlockControls>
<button />
<Button />
<DropdownMenu />
</BlockControls> After <BlockControls>
<ToolbarItem as="button" />
<ToolbarButton />
<ToolbarItem>
{ ( itemProps ) => ( <DropdownMenu toggleProps={ itemProps } /> ) }
</ToolbarItem>
</BlockControls> |
I didn't realize that few of them were 5.5 related. Thank you @gziolo for the link. |
@diegohaz Do you think we can have a before -> after snippet of code? |
Updated my comment. Please, let me know if it's clear enough or there's a better example/wording that could be used (the linked documentation on each component provides more detailed information). |
Thanks Diego, that's perfect. |
Dev notes for Refactor reusable blocks to not depend on the editor module - #25853 Reusable blocks now live in @wordpress/reusable-blocks which makes them... reusable in any block editorReusable blocks are an experimental feature available in the post editor. To make them available in other editors, they were moved to a separate package called import { ReusableBlocksMenuItems } from '@wordpress/reusable-blocks';
const { __experimentalReusableBlocks } = useSelect(
( select ) => select( 'core' ).getEntityRecords(
'postType',
'wp_block',
)
);
return (
<BlockEditorProvider
settings={ {
...settings,
__experimentalReusableBlocks,
} }
{ ...props } // value, onInput, onChange, etc.
>
<ReusableBlocksMenuItems />
{ children }
</BlockEditorProvider>
); |
We discussed this for the previous version and determined that it's not needed since it's still experimental. |
@adamziel: The feature isn't experimental, just some of the APIs surrounding it 🙂 |
Dev note for new Block API There is a new Block API
|
https://github.com/WordPress/gutenberg/issues?q=label%3A%22Needs+Dev+Note%22
These are all the PRs that need Dev Notes to be written for. Please share them here as comments, see what is related, and create make/core posts accordingly. Please let me know if you're unable to write a note for our PR. The notes should be posted before WP 5.6 RC, but the sooner, the better.
@adamziel
@youknowriad
Add Custom CSS support to the Group block - Add Custom CSS support to the Group block #25413Support custom units on theme.json - Support custom units on theme.json #25217_fields
data reuse for entities - Core Data: Implement_fields
data reuse for entities #19498@noisysocks
Widgets editor: Overview of documentation - Add technical documentation #25759@ellatrix
@aristath
px
values in front-facing styles to relative (em
) units - Convert allpx
values in front-facing styles to relative (em
) units #24523@jorgefilipecosta
@diegohaz
@vindl
Site Editor: make close button replaceable - Site Editor: make close button replaceable #22001@ntsekouras
The text was updated successfully, but these errors were encountered: