WordPress 6.7 compatibility: Add __nextHasNoMarginBottom to remaining BaseControl based components #39823
Labels
[Focus] Blocks
Issues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack
[Plugin] Jetpack
Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/
[Type] Task
In WordPress 6.7, deprecation notices will start to be logged for BaseControl-based components.
We need to check all use-cases of these components in the Jetpack monorepo and apply
__nextHasNoMarginBottom
.Technically we don't need to opt in to the new margin-free styles, but since the margins will be removed in a later release (and deprecation notices logged until then), it would be worth checking these instances to see if there are any display discrepancies as well.
An initial effort was done here: #39176. As a current example, when adding a VideoPress block and uploading a video there are two, related to
wp.components.ToggleControl
andwp.components.RangeControl
:Script debug does need to be enabled in
wp-config.php
:define( 'SCRIPT_DEBUG', true );
though (and at the moment, WordPress 6.7 on a test site using the WordPress Beta Tester plugin).More info: https://make.wordpress.org/core/2024/10/18/editor-components-updates-in-wordpress-6-7/#bottom-margin-styles-are-deprecated-39358
The text was updated successfully, but these errors were encountered: