diff --git a/.github/workflows/unit-test.yml b/.github/workflows/unit-test.yml
index b80804b824e3cd..c0f70070908c1c 100644
--- a/.github/workflows/unit-test.yml
+++ b/.github/workflows/unit-test.yml
@@ -135,9 +135,7 @@ jobs:
uses: actions/upload-artifact@65462800fd760344b1a7b4382951275a0abb4808 # v4.3.3
with:
name: build-assets
- path: |
- ./build/
- ./build-module/
+ path: ./build/
test-php:
name: PHP ${{ matrix.php }}${{ matrix.multisite && ' multisite' || '' }}${{ matrix.wordpress != '' && format( ' (WP {0}) ', matrix.wordpress ) || '' }} on ubuntu-latest
@@ -214,6 +212,7 @@ jobs:
uses: actions/download-artifact@fa0a91b85d4f404e444e00e005971372dc801d16 # v4.1.8
with:
name: build-assets
+ path: ./build
- name: Docker debug information
run: |
diff --git a/backport-changelog/6.7/7360.md b/backport-changelog/6.7/7360.md
deleted file mode 100644
index b2fb8efd624b93..00000000000000
--- a/backport-changelog/6.7/7360.md
+++ /dev/null
@@ -1,3 +0,0 @@
-https://github.com/WordPress/wordpress-develop/pull/7360
-
-* https://github.com/WordPress/gutenberg/pull/65460
diff --git a/changelog.txt b/changelog.txt
index b04fa0e9bbf8e2..dca31f9afc622e 100644
--- a/changelog.txt
+++ b/changelog.txt
@@ -1,280 +1,5 @@
== Changelog ==
-= 19.3.0-rc.2 =
-
-## Changelog
-
-### Features
-
-#### Zoom Out
-- Remove experimental flag. ([65404](https://github.com/WordPress/gutenberg/pull/65404))
-
-### Enhancements
-
-- Create Block: Update the minimum required PHP version to 7.2. ([65166](https://github.com/WordPress/gutenberg/pull/65166))
-- DataViews: remove unused `.dataviews-view-table__cell-content-wrapper:Empty` style rule. ([65084](https://github.com/WordPress/gutenberg/pull/65084))
-- Media Utils: Add TypeScript support and export more utils. ([64784](https://github.com/WordPress/gutenberg/pull/64784))
-- Media placeholders: Add "drag" to the text. ([65149](https://github.com/WordPress/gutenberg/pull/65149))
-- Restore: Move to trash button in Document settings. ([65087](https://github.com/WordPress/gutenberg/pull/65087))
-- Inspector Controls: Use custom block name in inspector controls when available. ([65398](https://github.com/WordPress/gutenberg/pull/65398))
-- Icons: Adds bell and bell-unread icons. ([65324](https://github.com/WordPress/gutenberg/pull/65324))
-- Editor topbar: Reorder the actions on the right. ([65163](https://github.com/WordPress/gutenberg/pull/65163))
-- Patterns: Add opt out preference to the 'Choose a Pattern' modal when adding a page. ([65026](https://github.com/WordPress/gutenberg/pull/65026))
-- Locked Templates: Blocks with contentOnly locking should not be transformable. ([64917](https://github.com/WordPress/gutenberg/pull/64917))
-- Block Locking: Add border to Replace item in content only image toolbar. ([64849](https://github.com/WordPress/gutenberg/pull/64849))
-
-#### Components
-- Styling: Apply elevation scale in components package. ([65159](https://github.com/WordPress/gutenberg/pull/65159))
-- Tabs: Improve Tabs indicator animation and related utils. ([64926](https://github.com/WordPress/gutenberg/pull/64926))
-- Modal
- - Add exit animation. ([65203](https://github.com/WordPress/gutenberg/pull/65203))
- - Decrease close button size. ([65131](https://github.com/WordPress/gutenberg/pull/65131))
-- Navigator Screen: Warn if path doesn't follow a URL-like scheme. ([65231](https://github.com/WordPress/gutenberg/pull/65231))
-- Card: Update Card radius. ([65053](https://github.com/WordPress/gutenberg/pull/65053))
-- Combobox Control: Add placeholder attribute. ([65254](https://github.com/WordPress/gutenberg/pull/65254))
-
-#### Block Library
-- Allow dropping multiple images to the image block. ([65030](https://github.com/WordPress/gutenberg/pull/65030))
-- Categories List block: Add dropdown for taxonomies. ([65272](https://github.com/WordPress/gutenberg/pull/65272))
-- Image: Adds the block controls for uploading image. ([64320](https://github.com/WordPress/gutenberg/pull/64320))
-- Remove colons from control labels. ([65205](https://github.com/WordPress/gutenberg/pull/65205))
-- Terms List block: Add Categories-specific variation. ([65434](https://github.com/WordPress/gutenberg/pull/65434))
-
-#### Zoom Out
-- Add Zoom Out toggle to editor header when experiment enabled. ([65183](https://github.com/WordPress/gutenberg/pull/65183))
-- Add prompt for drag and drop in Patterns tab in Zoom Out mode. ([65115](https://github.com/WordPress/gutenberg/pull/65115))
-- Close inserter on exiting Zoom Out to edit. ([65194](https://github.com/WordPress/gutenberg/pull/65194))
-- Show top level sections in List View. ([65202](https://github.com/WordPress/gutenberg/pull/65202))
-- Try vertical displacement when dragging a pattern between existing patterns/sections. ([63896](https://github.com/WordPress/gutenberg/pull/63896))
-
-#### Block Editor
-- Link Editing: Automatically add tel to phone number when linking URL. ([64865](https://github.com/WordPress/gutenberg/pull/64865))
-thub.com/WordPress/gutenberg/pull/65300))
-- Drag and Drop: When dragging a mix of video, audio, and image blocks, create individual blocks as appropriate. ([65144](https://github.com/WordPress/gutenberg/pull/65144))
-- URLInput: Replace input with InputControl. ([65158](https://github.com/WordPress/gutenberg/pull/65158))
-- Normalize block inspector controls spacing. ([64526](https://github.com/WordPress/gutenberg/pull/64526))
-
-#### Post Editor
-- Add new Media section to preferences modal. ([64846](https://github.com/WordPress/gutenberg/pull/64846))
-- DocumentBar: Replace icon with post type label. ([65170](https://github.com/WordPress/gutenberg/pull/65170))
-- Page editor: Double-click to edit template part. ([65024](https://github.com/WordPress/gutenberg/pull/65024))
-- Post publish upload media dialog: Handle more block types. ([65122](https://github.com/WordPress/gutenberg/pull/65122))
-
-#### Block bindings
-- Populate block context with inherited post type from template slug. ([65062](https://github.com/WordPress/gutenberg/pull/65062))
-- Try gap 0 on attribute items. ([65277](https://github.com/WordPress/gutenberg/pull/65277))
-- Use post meta label from `register_meta` in block bindings workflows. ([65099](https://github.com/WordPress/gutenberg/pull/65099))
-
-#### Global Styles
-- Refactor site background controls and move site global styles into Background group. ([65304](https://github.com/WordPress/gutenberg/pull/65304))
-- Spacing control: Replace sides dropdwon with link button. ([65193](https://github.com/WordPress/gutenberg/pull/65193))
-
-#### Data Views
-- DataViews Sidebar: Display item count on DataViews sidebar. ([65223](https://github.com/WordPress/gutenberg/pull/65223))
-- DataViews: Improve UX of bundled views for Pages. ([65295](https://github.com/WordPress/gutenberg/pull/65295))
-
-#### Interactivity API
-- Refactor context proxies. ([64713](https://github.com/WordPress/gutenberg/pull/64713))
-- Update: Rephrase "Force page reload" and move to Advanced. ([65081](https://github.com/WordPress/gutenberg/pull/65081))
-
-#### REST API
-- Global Styles: Allow read access to users with `edit_posts` capabilities. ([65071](https://github.com/WordPress/gutenberg/pull/65071))
-- Query loop / Post template: Enable post format filter. ([64167](https://github.com/WordPress/gutenberg/pull/64167))
-
-### New APIs
-- Add @wordpress/fields package.
- - Introduce the package. ([65230](https://github.com/WordPress/gutenberg/pull/65230))
- - Make the package private. ([65269](https://github.com/WordPress/gutenberg/pull/65269))
-- Interactivity API: Add `getServerState()` and `getServerContext()`. ([65151](https://github.com/WordPress/gutenberg/pull/65151))
-
-### Bug Fixes
-
-- Align popover alt variant styling with block toolbar. ([65263](https://github.com/WordPress/gutenberg/pull/65263))
-- Compose: Correctly call timer cleanup in 'useFocusOnMount'. ([65184](https://github.com/WordPress/gutenberg/pull/65184))
-- Fix some docblock types related to the Template Registration API. ([65187](https://github.com/WordPress/gutenberg/pull/65187))
-- Fix the issue where block spacing control not shown. ([65371](https://github.com/WordPress/gutenberg/pull/65371))
-- Fix unintentional block toolbar shadow. ([65182](https://github.com/WordPress/gutenberg/pull/65182))
-- Fix: Moving a page to the trash on the site editor does not goes back to the pages list. ([65119](https://github.com/WordPress/gutenberg/pull/65119))
-- Fix: Moving the last page item to the the trash causes a crash. ([65236](https://github.com/WordPress/gutenberg/pull/65236))
-- Preferences: Fix back button on mobile. ([65141](https://github.com/WordPress/gutenberg/pull/65141))
-- Post Summary Panel: Restore `height:Auto` for toggle buttons. ([65362](https://github.com/WordPress/gutenberg/pull/65362))
-- Fix Tabs styling in Font Library modal. ([65330](https://github.com/WordPress/gutenberg/pull/65330))
-- E2E: Change deprecated social icons for standard in end-to-end. ([65312](https://github.com/WordPress/gutenberg/pull/65312))
-- Typography: Make title blocks apply typographic styles consistently. ([65307](https://github.com/WordPress/gutenberg/pull/65307))
-- Target Hints REST API: Add missing param sanitization. ([65280](https://github.com/WordPress/gutenberg/pull/65280))
-- Interactivity API: Update iterable signals when `deepMerge()` adds new properties. ([65135](https://github.com/WordPress/gutenberg/pull/65135))
-- Navigation Menus: Typography styling support to the navigation submenu block. ([65060](https://github.com/WordPress/gutenberg/pull/65060))
-- Grid: In RTL languages, the resize handles point in the opposite direction. ([64995](https://github.com/WordPress/gutenberg/pull/64995))
-- Block Locking: Fix Content Only Toolbar icon focus style. ([64940](https://github.com/WordPress/gutenberg/pull/64940))
-- Image: Fix resizing to max width in classic themes. ([64819](https://github.com/WordPress/gutenberg/pull/64819))
-- Meta Boxes: Try split content view. ([64351](https://github.com/WordPress/gutenberg/pull/64351))
-- Distraction Free: Fix blurry edge along editor header. ([64277](https://github.com/WordPress/gutenberg/pull/64277))
-
-#### Block Library
-- Comments Pagination: Fix warning returned by comments pagination blocks. ([65435](https://github.com/WordPress/gutenberg/pull/65435))
-- Cover: Explicitly set isUserOverlayColor to false when media is updated. ([65105](https://github.com/WordPress/gutenberg/pull/65105))
-- Disallow setting grid block rows/columns to zero. ([65217](https://github.com/WordPress/gutenberg/pull/65217))
-- Fix image block crash. ([65222](https://github.com/WordPress/gutenberg/pull/65222))
-- Fix: Buttons block: Block spacing value does not apply to both vertical and horizontal alignment. ([64971](https://github.com/WordPress/gutenberg/pull/64971))
-- Fix: Embed blocks: Figcaption inserted via toolbar not nested within figure element - #64960. ([64970](https://github.com/WordPress/gutenberg/pull/64970))
-- Image cropping: Skip making an API request if there are no changes to apply. ([65384](https://github.com/WordPress/gutenberg/pull/65384))
-- Comments Pagination: Pass the comments query `paged` arg to functions `get_next_comments_link` and `get_previous_comments_link`. ([63698](https://github.com/WordPress/gutenberg/pull/63698))
-- Query Loop
- - Default to querying posts when on singular content. ([65067](https://github.com/WordPress/gutenberg/pull/65067))
- - Remove is_singular() check and fix test. ([65483](https://github.com/WordPress/gutenberg/pull/65483))
-
-#### Block Editor
-- Inserter: Fix loading indicator for reusable blocks. ([64839](https://github.com/WordPress/gutenberg/pull/64839))
-- Normalize spacing in Layout hook controls. ([65132](https://github.com/WordPress/gutenberg/pull/65132))
-- Pattern Inserter: Fix pattern list overflow. ([65192](https://github.com/WordPress/gutenberg/pull/65192))
-- Remove reset styles RTL from the iframe. ([65150](https://github.com/WordPress/gutenberg/pull/65150))
-- Revert "Block Insertion: Clear the insertion point when selecting a d…. ([65208](https://github.com/WordPress/gutenberg/pull/65208))
-
-#### Components
-- BoxControl: Unify input filed width whether linked or not. ([65348](https://github.com/WordPress/gutenberg/pull/65348))
-- ComboboxControl: Add more unit tests. ([65255](https://github.com/WordPress/gutenberg/pull/65255))
-- Fix: Button Replace remaining 40px default size violations [Edit widgets]. ([65367](https://github.com/WordPress/gutenberg/pull/65367))
-- Tabs: Fix vertical indicator. ([65385](https://github.com/WordPress/gutenberg/pull/65385))
-
-#### Block bindings
-- Fix empty strings placeholders in post meta bindings. ([65089](https://github.com/WordPress/gutenberg/pull/65089))
-- Remove key fallback in bindings get values and rely on source label. ([65517](https://github.com/WordPress/gutenberg/pull/65517))
-
-#### Zoom Out
-- Force device type to Desktop whenever zoom out is invoked. ([64476](https://github.com/WordPress/gutenberg/pull/64476))
-- Hide toolbar icon on smaller viewports. ([65437](https://github.com/WordPress/gutenberg/pull/65437))
-- Remove zoom out toggle when editor is not iframed. ([65452](https://github.com/WordPress/gutenberg/pull/65452))
-
-### Accessibility
-
-- A11y: Add script-module. ([65101](https://github.com/WordPress/gutenberg/pull/65101))
-- Interactivity API: Use a11y Script Module in Gutenberg. ([65123](https://github.com/WordPress/gutenberg/pull/65123))
-- Script Modules API: Print script module live regions HTML in page HTML. ([65380](https://github.com/WordPress/gutenberg/pull/65380))
-- DatePicker: Better hover/focus styles. ([65117](https://github.com/WordPress/gutenberg/pull/65117))
-- Form Input: Don't use `flex-direction: Row-reverse` for checkbox field. ([64232](https://github.com/WordPress/gutenberg/pull/64232))
-- Navigation Menus: Remove Warning and add notice for Navigation. ([63921](https://github.com/WordPress/gutenberg/pull/63921))
-- Global Styles: Fix the shadows Range control accessibility and usability. ([63908](https://github.com/WordPress/gutenberg/pull/63908))
-- Block Editor: Fix accessibility of the hooked blocks toggles. ([63133](https://github.com/WordPress/gutenberg/pull/63133))
-
-
-#### Post Editor
-- Support keyboard resizing of meta boxes pane. ([65325](https://github.com/WordPress/gutenberg/pull/65325))
-- Swap position of the Pre-publish checks buttons. ([65317](https://github.com/WordPress/gutenberg/pull/65317))
-
-
-### Performance
-
-- Core Data: Batch remaining actions in resolvers. ([65176](https://github.com/WordPress/gutenberg/pull/65176))
-- Block Editor: Use static access for selector in 'useZoomOutModeExit'. ([65337](https://github.com/WordPress/gutenberg/pull/65337))
-- Editor: Optimize global styles permission check. ([65177](https://github.com/WordPress/gutenberg/pull/65177))
-
-
-### Experiments
-
-- Block bindings REST API: Bring bindings UI in Site Editor. ([64072](https://github.com/WordPress/gutenberg/pull/64072))
-
-
-### Documentation
-
-- Add JSDoc block for getSectionRootClientId in block editor package. ([65219](https://github.com/WordPress/gutenberg/pull/65219))
-- ButtonGroup: Fix story to show what the component does. ([65336](https://github.com/WordPress/gutenberg/pull/65336))
-- DataViews storybook
- - Better styles for combined fields story. ([65078](https://github.com/WordPress/gutenberg/pull/65078))
- - Enable all layouts for combined fields storybook. ([65082](https://github.com/WordPress/gutenberg/pull/65082))
-- Docs: Fix minor typos in Build your first block tutorial. ([64961](https://github.com/WordPress/gutenberg/pull/64961))
-- Docs: Update the content of the API version 3 section in the Block API Reference. ([65375](https://github.com/WordPress/gutenberg/pull/65375))
-- Fix typo in Slot Fills documentation. ([65275](https://github.com/WordPress/gutenberg/pull/65275))
-
-
-### Code Quality
-
-- Components: Transition to the new 40px default size.
- - Button:
- - Add __next40pxDefaultSize for files in editor 3. ([65139](https://github.com/WordPress/gutenberg/pull/65139))
- - Add __next40pxDefaultSize for files in editor 4. ([65140](https://github.com/WordPress/gutenberg/pull/65140))
- - Add props for buttons in editor 1. ([65068](https://github.com/WordPress/gutenberg/pull/65068))
- - Add props for buttons in editor 2. ([65083](https://github.com/WordPress/gutenberg/pull/65083))
- - Fix: Replace remaining 40px default size violations [Block Editor 4]. ([65257](https://github.com/WordPress/gutenberg/pull/65257))
- - Fix: Replace remaining 40px default size violation [Block library 3]. ([65110](https://github.com/WordPress/gutenberg/pull/65110))
- - Fix: Replace remaining 40px default size violation [Block library 4]. ([65143](https://github.com/WordPress/gutenberg/pull/65143))
- - Fix: Replace remaining 40px default size violation [Block library]. ([65075](https://github.com/WordPress/gutenberg/pull/65075))
- - Fix: Replace remaining 40px default size violation [Edit Site 2]. ([65258](https://github.com/WordPress/gutenberg/pull/65258))
- - Fix: Replace remaining 40px default size violations [Block library 1]. ([65033](https://github.com/WordPress/gutenberg/pull/65033))
- - Fix: Replace remaining 40px default size violations [Block Editor 1]. ([65034](https://github.com/WordPress/gutenberg/pull/65034))
- - BoxControl
- - Add lint rule for 40px size prop usage. ([65341](https://github.com/WordPress/gutenberg/pull/65341))
- - DimensionsPanel: Apply 40px default size to UI when no spacing preset is available. ([65300](https://github.com/WordPress/gutenberg/pull/65300))
-- Add `useEvent` and revamped `useResizeObserver` to `@wordpress/compose`. ([64943](https://github.com/WordPress/gutenberg/pull/64943))
-- DataViews: Use Dropdown for views configuration dialog. ([65314](https://github.com/WordPress/gutenberg/pull/65314))
-- Platform docs: Upgrade dependencies. ([65445](https://github.com/WordPress/gutenberg/pull/65445))
-- Rename edit-post__fade-in-animation and unify keyframe definitions. ([65377](https://github.com/WordPress/gutenberg/pull/65377))
-- Update minimum required version in PHP. ([65301](https://github.com/WordPress/gutenberg/pull/65301))
-- Editor: Use hooks instead of HoC in `BlockManager`. ([65349](https://github.com/WordPress/gutenberg/pull/65349))
-- Data Views Fields: Migrate store and actions from editor package to fields package. ([65261](https://github.com/WordPress/gutenberg/pull/65261))
-- Plugin: Remove 'function_exists' checks for methods with 'gutenberg' prefix. ([65260](https://github.com/WordPress/gutenberg/pull/65260))
-- Global Styles: Update REST controller override method and backport changes from Core. ([65259](https://github.com/WordPress/gutenberg/pull/65259))
-- Patterns: Remove unused method returned from 'mapSelect'. ([65073](https://github.com/WordPress/gutenberg/pull/65073))
-- Embed: Convert EmbedPreview component to functional component. ([51325](https://github.com/WordPress/gutenberg/pull/51325))
-
-#### Components
-- BoxControl: Fix critical error when null value is passed. ([65287](https://github.com/WordPress/gutenberg/pull/65287))
-- Composite:
- - Deprecate legacy, unstable version. ([63572](https://github.com/WordPress/gutenberg/pull/63572))
- - Remove store prop and useCompositeStore hook. ([64723](https://github.com/WordPress/gutenberg/pull/64723))
- - Stabilize APIs. ([63569](https://github.com/WordPress/gutenberg/pull/63569))
-- `@wordpress/components`: Add local copy of `use-lilius`. ([65097](https://github.com/WordPress/gutenberg/pull/65097))
-
-#### Block bindings
-- Always prioritize using context in post meta source logic. ([65449](https://github.com/WordPress/gutenberg/pull/65449))
-- Improve getRegisteredPostMeta resolver. ([65450](https://github.com/WordPress/gutenberg/pull/65450))
-- Remove extra filtering of empty sources. ([65447](https://github.com/WordPress/gutenberg/pull/65447))
-
-#### Block Editor
-- Remove the 'PrivateInserter' component. ([65111](https://github.com/WordPress/gutenberg/pull/65111))
-- Use the tooltip from a button in 'ButtonBlockAppender'. ([65113](https://github.com/WordPress/gutenberg/pull/65113))
-- Remove unused css selectors. ([65276](https://github.com/WordPress/gutenberg/pull/65276))
-
-### Tools
-
-- Scripts: Update stylelint dependency and the default configuration. ([64828](https://github.com/WordPress/gutenberg/pull/64828))
-- Styleling config: Fix stylelint configuration missing files for npm. ([65313](https://github.com/WordPress/gutenberg/pull/65313))
-
-#### Build Tooling
-- Build Plugin: Simplify and improve zip contents. ([65232](https://github.com/WordPress/gutenberg/pull/65232))
-- Build zip artifact on release and wp production branches. ([65471](https://github.com/WordPress/gutenberg/pull/65471))
-- Build: Include Core blocks' `render` and `variations` files. ([63311](https://github.com/WordPress/gutenberg/pull/63311))
-- Script Modules
- - Prepare build for more script modules. ([65064](https://github.com/WordPress/gutenberg/pull/65064))
- - Remove babel from script-modules build. ([65279](https://github.com/WordPress/gutenberg/pull/65279))
- - Remove es-module shims and importmap-polyfill. ([65210](https://github.com/WordPress/gutenberg/pull/65210))
-- Correctly generate PHP files for server-side rendering of blocks on Windows OS. ([65248](https://github.com/WordPress/gutenberg/pull/65248))
-- Packages: Only add polyfills where needed. ([65292](https://github.com/WordPress/gutenberg/pull/65292))
-- Switch from UglifyJS to Terser to build the polyfill script. ([65278](https://github.com/WordPress/gutenberg/pull/65278))
-
-#### Testing
-- Unit tests: Mock matchMedia to enforce prefers-reduce-motion. ([65438](https://github.com/WordPress/gutenberg/pull/65438))
-- Upgrade Playwright to v1.47. ([65156](https://github.com/WordPress/gutenberg/pull/65156))
-
-## First-time contributors
-
-The following PRs were merged by first-time contributors:
-
-- @AKSHAT2802: Add __next40pxDefaultSize for files in editor 4. ([65140](https://github.com/WordPress/gutenberg/pull/65140))
-- @devansh016: Automatically add tel to phone number when linking URL. ([64865](https://github.com/WordPress/gutenberg/pull/64865))
-- @dhruvang21: Fix: Button Replace remaining 40px default size violations [Edit widgets]. ([65367](https://github.com/WordPress/gutenberg/pull/65367))
-- @farid-hadi: Docs: Fix minor typos in Build your first block tutorial. ([64961](https://github.com/WordPress/gutenberg/pull/64961))
-- @greenworld: Fix typo in Slot Fills documentation. ([65275](https://github.com/WordPress/gutenberg/pull/65275))
-- @louwie17: Convert EmbedPreview component to functional component. ([51325](https://github.com/WordPress/gutenberg/pull/51325))
-- @rahulharpal1603: URLInput: Replace input with InputControl. ([65158](https://github.com/WordPress/gutenberg/pull/65158))
-
-
-## Contributors
-
-The following contributors merged PRs in this release:
-
-@aaronrobertshaw @afercia @AKSHAT2802 @Aljullu @andrewserong @carolinan @cbravobernal @ciampo @colorful-tones @creativecoder @DaniGuardiola @DAreRodz @devansh016 @dhruvang21 @ellatrix @farid-hadi @getdave @gigitux @greenworld @gziolo @hbhalodia @jameskoster @jasmussen @javierarce @jeryj @jorgefilipecosta @jsnajdr @kevin940726 @louwie17 @madhusudhand @MaggieCabrera @Mamaduka @mikeybinns @mirka @ntsekouras @oandregal @ockham @peterwilsoncc @rahulharpal1603 @ramonjd @richtabor @rohitmathur-7 @SantosGuillamot @scruffian @sgomes @sirreal @stokesman @swissspidy @t-hamano @talldan @vipul0425 @zaguiini
-
-
= 19.3.0-rc.1 =
## Changelog
diff --git a/docs/manifest.json b/docs/manifest.json
index d76717fbdedfc1..d7f74d47995b63 100644
--- a/docs/manifest.json
+++ b/docs/manifest.json
@@ -521,12 +521,6 @@
"markdown_source": "../docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md",
"parent": "core-concepts"
},
- {
- "title": "Using TypeScript",
- "slug": "using-typescript",
- "markdown_source": "../docs/reference-guides/interactivity-api/core-concepts/using-typescript.md",
- "parent": "core-concepts"
- },
{
"title": "Quick start guide",
"slug": "iapi-quick-start-guide",
diff --git a/docs/reference-guides/data/data-core-block-editor.md b/docs/reference-guides/data/data-core-block-editor.md
index 4b3ca78f74d299..c6552ef431cef8 100644
--- a/docs/reference-guides/data/data-core-block-editor.md
+++ b/docs/reference-guides/data/data-core-block-editor.md
@@ -857,10 +857,16 @@ _Returns_
### hasBlockMovingClientId
-> **Deprecated**
-
Returns whether block moving mode is enabled.
+_Parameters_
+
+- _state_ `Object`: Editor state.
+
+_Returns_
+
+- `string`: Client Id of moving block.
+
### hasDraggedInnerBlock
Returns true if one of the block's inner blocks is dragged.
@@ -1655,13 +1661,11 @@ _Returns_
### setBlockMovingClientId
-> **Deprecated**
-
-Set the block moving client ID.
+Action that enables or disables the block moving mode.
-_Returns_
+_Parameters_
-- `Object`: Action object.
+- _hasBlockMovingClientId_ `string|null`: Enable/Disable block moving mode.
### setBlockVisibility
diff --git a/docs/reference-guides/interactivity-api/core-concepts/README.md b/docs/reference-guides/interactivity-api/core-concepts/README.md
index 695a4d622f6c52..f4e6891c4ff165 100644
--- a/docs/reference-guides/interactivity-api/core-concepts/README.md
+++ b/docs/reference-guides/interactivity-api/core-concepts/README.md
@@ -7,5 +7,3 @@ This section provides some guides on important concepts and mental models relate
2. **[Understanding global state, local context and derived state](/docs/reference-guides/interactivity-api/core-concepts/undestanding-global-state-local-context-and-derived-state.md):** The guide explains how to effectively use global state, local context, and derived state within the Interactivity API emphasizing the importance of choosing the appropriate state management technique based on the scope and requirements of your data.
3. **[Server-side rendering: Processing directives on the server](/docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md):** The Interactivity API allows WordPress to use server-side rendering to create interactive and state-aware HTML, smoothly connected with client-side features while maintaining performance and SEO benefits.
-
-4. **[Using TypeScript](/docs/reference-guides/interactivity-api/core-concepts/using-typescript.md):** This guide will walk you through the process of using TypeScript with Interactivity API stores, covering everything from basic type definitions to advanced techniques for handling complex store structures.
diff --git a/docs/reference-guides/interactivity-api/core-concepts/using-typescript.md b/docs/reference-guides/interactivity-api/core-concepts/using-typescript.md
deleted file mode 100644
index ed0bdd88211d11..00000000000000
--- a/docs/reference-guides/interactivity-api/core-concepts/using-typescript.md
+++ /dev/null
@@ -1,746 +0,0 @@
-# Using TypeScript
-
-The Interactivity API provides robust support for TypeScript, enabling developers to build type-safe stores to enhance the development experience with static type checking, improved code completion, and simplified refactoring. This guide will walk you through the process of using TypeScript with Interactivity API stores, covering everything from basic type definitions to advanced techniques for handling complex store structures.
-
-These are the core principles of TypeScript's interaction with the Interactivity API:
-
-- **Inferred client types**: When you create a store using the `store` function, TypeScript automatically infers the types of the store's properties (`state`, `actions`, etc.). This means that you can often get away with just writing plain JavaScript objects, and TypeScript will figure out the types for you.
-- **Explicit server types**: When dealing with data defined on the server, like local context or the initial values of the global state, you can explicitly define its types to ensure that everything is correctly typed.
-- **Mutiple store parts**: Even if your store is split into multiple parts, you can define or infer the types of each part of the store and then merge them into a single type that represents the entire store.
-- **Typed external stores**: You can import typed stores from external namespaces, allowing you to use other plugins' functionality with type safety.
-
-## Installing `@wordpress/interactivity` locally
-
-If you haven't done so already, you need to install the package `@wordpress/interactivity` locally so TypeScript can use its types in your IDE. You can do this using the following command:
-
-`npm install @wordpress/interactivity`
-
-It is also a good practice to keep that package updated.
-
-## Scaffolding a new typed interactive block
-
-If you want to explore an example of an interactive block using TypeScript in your local environment, you can use the `@wordpress/create-block-interactive-template`.
-
-Start by ensuring you have Node.js and `npm` installed on your computer. Review the [Node.js development environment](https://developer.wordpress.org/block-editor/getting-started/devenv/nodejs-development-environment/) guide if not.
-
-Next, use the [`@wordpress/create-block`](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-create-block/) package and the [`@wordpress/create-block-interactive-template`](https://www.npmjs.com/package/@wordpress/create-block-interactive-template) template to scaffold the block.
-
-Choose the folder where you want to create the plugin, execute the following command in the terminal from within that folder, and choose the `typescript` variant when asked.
-
-```
-npx @wordpress/create-block@latest --template @wordpress/create-block-interactive-template
-```
-
-**Important**: Do not provide a slug in the terminal. Otherwise, `create-block` will not ask you which variant you want to choose and it will select the default non-TypeScript variant by default.
-
-Finally, you can keep following the instructions in the [Getting Started Guide](https://developer.wordpress.org/block-editor/reference-guides/interactivity-api/iapi-quick-start-guide/) as the rest of the instructions remain the same.
-
-## Typing the store
-
-Depending on the structure of your store and your preference, there are three options you can choose from to generate your store's types:
-
-1. Infer the types from your client store definition.
-2. Manually type the server state, but infer the rest from your client store definition.
-3. Manually write all the types.
-
-### 1. Infer the types from your client store definition
-
-When you create a store using the `store` function, TypeScript automatically infers the types of the store's properties (`state`, `actions`, `callbacks`, etc.). This means that you can often get away with just writing plain JavaScript objects, and TypeScript will figure out the correct types for you.
-
-Let's start with a basic example of a counter block. We will define the store in the `view.ts` file of the block, which contains the initial global state, an action and a callback.
-
-```ts
-// view.ts
-const myStore = store( 'myCounterPlugin', {
- state: {
- counter: 0,
- },
- actions: {
- increment() {
- myStore.state.counter += 1;
- },
- },
- callbacks: {
- log() {
- console.log( `counter: ${ myStore.state.counter }` );
- },
- },
-} );
-```
-
-If you inspect the types of `myStore` using TypeScript, you will see that TypeScript has been able to infer the types correctly.
-
-```ts
-const myStore: {
- state: {
- counter: number;
- };
- actions: {
- increment(): void;
- };
- callbacks: {
- log(): void;
- };
-};
-```
-
-You can also destructure the `state`, `actions` and `callbacks` properties, and the types will still work correctly.
-
-```ts
-const { state } = store( 'myCounterPlugin', {
- state: {
- counter: 0,
- },
- actions: {
- increment() {
- state.counter += 1;
- },
- },
- callbacks: {
- log() {
- console.log( `counter: ${ state.counter }` );
- },
- },
-} );
-```
-
-In conclusion, inferring the types is useful when you have a simple store defined in a single call to the `store` function and you do not need to type any state that has been initialized on the server.
-
-### 2. Manually type the server state, but infer the rest from your client store definition
-
-The global state that is initialized on the server with the `wp_interactivity_state` function doesn't exist on your client store definition and, therefore, needs to be manually typed. But if you don't want to define all the types of your store, you can infer the types of your client store definition and merge them with the types of your server initialized state.
-
-_Please, visit [the Server-side Rendering guide](/docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md) to learn more about `wp_interactivity_state` and how directives are processed on the server._
-
-Following our previous example, let's move our `counter` state initialization to the server.
-
-```php
-wp_interactivity_state( 'myCounterPlugin', array(
- 'counter' => 1,
-));
-```
-
-Now, let's define the server state types and merge it with the types inferred from the client store definition.
-
-```ts
-// Types the server state.
-type ServerState = {
- state: {
- counter: number;
- };
-};
-
-// Defines the store in a variable to be able to extract its type later.
-const storeDef = {
- actions: {
- increment() {
- state.counter += 1;
- },
- },
- callbacks: {
- log() {
- console.log( `counter: ${ state.counter }` );
- },
- },
-};
-
-// Merges the types of the server state and the client store definition.
-type Store = ServerState & typeof storeDef;
-
-// Injects the final types when calling the `store` function.
-const { state } = store< Store >( 'myCounterPlugin', storeDef );
-```
-
-Alternatively, if you don't mind typing the entire state including both the values defined on the server and the values defined on the client, you can cast the `state` property and let TypeScript infer the rest of the store.
-
-Let's imagine you have an additional property in the client global state called `product`.
-
-```ts
-type State = {
- counter: number; // The server state.
- product: number; // The client state.
-};
-
-const { state } = store( 'myCounterPlugin', {
- state: {
- product: 2,
- } as State, // Casts the entire state manually.
- actions: {
- increment() {
- state.counter * state.product;
- },
- },
-} );
-```
-
-That's it. Now, TypeScript will infer the types of the `actions` and `callbacks` properties from the store definition, but it will use the type `State` for the `state` property so it contains the correct types from both the client and server definitions.
-
-In conclusion, this approach is useful when you have a server state that needs to be manually typed, but you still want to infer the types of the rest of the store.
-
-### 3. Manually write all the types
-
-If you prefer to define all the types of the store manually instead of letting TypeScript infer them from your client store definition, you can do that too. You simply need to pass them to the `store` function.
-
-```ts
-// Defines the store types.
-interface Store {
- state: {
- counter: number; // Initial server state
- };
- actions: {
- increment(): void;
- };
- callbacks: {
- log(): void;
- };
-}
-
-// Pass the types when calling the `store` function.
-const { state } = store< Store >( 'myCounterPlugin', {
- actions: {
- increment() {
- state.counter += 1;
- },
- },
- callbacks: {
- log() {
- console.log( `counter: ${ state.counter }` );
- },
- },
-} );
-```
-
-That's it! In conclusion, this approach is useful when you want to control all the types of your store and you don't mind writing them by hand.
-
-## Typing the local context
-
-The initial local context is defined on the server using the `data-wp-context` directive.
-
-```html
-
...
-```
-
-For that reason, you need to define its type manually and pass it to the `getContext` function to ensure the returned properties are correctly typed.
-
-```ts
-// Defines the types of your context.
-type MyContext = {
- counter: number;
-};
-
-store( 'myCounterPlugin', {
- actions: {
- increment() {
- // Passes it to the getContext function.
- const context = getContext< MyContext >();
- // Now `context` is properly typed.
- context.counter += 1;
- },
- },
-} );
-```
-
-To avoid having to pass the context types over and over, you can also define a typed function and use that function instead of `getContext`.
-
-```ts
-// Defines the types of your context.
-type MyContext = {
- counter: number;
-};
-
-// Defines a typed function. You only have to do this once.
-const getMyContext = getContext< MyContext >;
-
-store( 'myCounterPlugin', {
- actions: {
- increment() {
- // Use your typed function.
- const context = getMyContext();
- // Now `context` is properly typed.
- context.counter += 1;
- },
- },
-} );
-```
-
-That's it! Now you can access the context properties with the correct types.
-
-## Typing the derived state
-
-The derived state is data that is calculated based on the global state or local context. In the client store definition, it is defined using a getter in the `state` object.
-
-_Please, visit the [Understanding global state, local context and derived state](./undestanding-global-state-local-context-and-derived-state.md) guide to learn more about how derived state works in the Interactivity API._
-
-Following our previous example, let's create a derived state that is the double of our counter.
-
-```ts
-type MyContext = {
- counter: number;
-};
-
-const myStore = store( 'myCounterPlugin', {
- state: {
- get double() {
- const { counter } = getContext< MyContext >();
- return counter * 2;
- },
- },
- actions: {
- increment() {
- state.counter += 1; // This type is number.
- },
- },
-} );
-```
-
-Normally, when the derived state depends on the local context, TypeScript will be able to infer the correct types:
-
-```ts
-const myStore: {
- state: {
- readonly double: number;
- };
- actions: {
- increment(): void;
- };
-};
-```
-
-But when the return value of the derived state depends directly on some part of the global state, TypeScript will not be able to infer the types because it will claim that it has a circular reference.
-
-For example, in this case, TypeScript cannot infer the type of `state.double` because it depends on `state.counter`, and the type of `state` is not completed until the type of `state.double` is defined, creating a circular reference.
-
-```ts
-const { state } = store( 'myCounterPlugin', {
- state: {
- counter: 0,
- get double() {
- // TypeScript can't infer this return type because it depends on `state`.
- return state.counter * 2;
- },
- },
- actions: {
- increment() {
- state.counter += 1; // This type is now unknown.
- },
- },
-} );
-```
-
-In this case, depending on your TypeScript configuration, TypeScript will either warn you about a circular reference or simply add the `any` type to the `state` property.
-
-However, solving this problem is easy; we simply need to manually provide TypeScript with the return type of that getter. Once we do that, the circular reference disappears, and TypeScript can once again infer all the `state` types.
-
-```ts
-const { state } = store( 'myCounterPlugin', {
- state: {
- counter: 1,
- get double(): number {
- return state.counter * 2;
- },
- },
- actions: {
- increment() {
- state.counter += 1; // Correctly inferred!
- },
- },
-} );
-```
-
-These are now the correct inferred types for the previous store.
-
-```ts
-const myStore: {
- state: {
- counter: number;
- readonly double: number;
- };
- actions: {
- increment(): void;
- };
-};
-```
-
-When using `wp_interactivity_state` in the server, remember that you also need to define the initial value of your derived state, like this:
-
-```php
-wp_interactivity_state( 'myCounterPlugin', array(
- 'counter' => 1,
- 'double' => 2,
-));
-```
-
-But if you are inferring the types, you don't need to manually define the type of the derived state because it already exists in your client's store definition.
-
-```ts
-// You don't need to type `state.double` here.
-type ServerState = {
- state: {
- counter: number;
- };
-};
-
-// The `state.double` type is inferred from here.
-const storeDef = {
- state: {
- get double(): number {
- return state.counter * 2;
- },
- },
- actions: {
- increment() {
- state.counter += 1;
- },
- },
-};
-
-// Merges the types of the server state and the client store definition.
-type Store = ServerState & typeof storeDef;
-
-// Injects the final types when calling the `store` function.
-const { state } = store< Store >( 'myCounterPlugin', storeDef );
-```
-
-That's it! Now you can access the derived state properties with the correct types.
-
-## Typing asynchronous actions
-
-Another thing to keep in mind when using TypeScript with the Interactivity API is that asynchronous actions must be defined with generators instead of async functions.
-
-The reason for using generators in the Interactivity API's asynchronous actions is to be able to restore the scope from the initially triggered action once the asynchronous action continues its execution after yielding. But this is a syntax change only, otherwise, **these functions operate just like regular async functions**, and the inferred types from the `store` function reflect this.
-
-Following our previous example, let's add an asynchronous action to the store.
-
-```ts
-const { state } = store( 'myCounterPlugin', {
- state: {
- counter: 0,
- get double(): number {
- return state.counter * 2;
- },
- },
- actions: {
- increment() {
- state.counter += 1;
- },
- *delayedIncrement() {
- yield new Promise( ( r ) => setTimeout( r, 1000 ) );
- state.counter += 1;
- },
- },
-} );
-```
-
-The inferred types for this store are:
-
-```ts
-const myStore: {
- state: {
- counter: number;
- readonly double: number;
- };
- actions: {
- increment(): void;
- // This behaves like a regular async function.
- delayedIncrement(): Promise< void >;
- };
-};
-```
-
-This also means that you can use your async actions in external functions, and TypeScript will correctly use the async function types.
-
-```ts
-const someAsyncFunction = async () => {
- // This works fine and it's correctly typed.
- await actions.delayedIncrement( 2000 );
-};
-```
-
-When you are not inferring types but manually writing the types for your entire store, you can use async function types for your async actions.
-
-```ts
-type Store = {
- state: {
- counter: number;
- readonly double: number;
- };
- actions: {
- increment(): void;
- delayedIncrement(): Promise< void >; // You can use async functions here.
- };
-};
-```
-
-There's something to keep in mind when when using asynchronous actions. Just like with the derived state, if the asynchronous action needs to return a value and this value directly depends on some part of the global state, TypeScript will not be able to infer the type due to a circular reference.
-
- ```ts
- const { state, actions } = store( 'myCounterPlugin', {
- state: {
- counter: 0,
- },
- actions: {
- *delayedReturn() {
- yield new Promise( ( r ) => setTimeout( r, 1000 ) );
- return state.counter; // TypeScript can't infer this return type.
- },
- },
- } );
- ```
-
- In this case, just as we did with the derived state, we must manually type the return value of the generator.
-
- ```ts
- const { state, actions } = store( 'myCounterPlugin', {
- state: {
- counter: 0,
- },
- actions: {
- *delayedReturn(): Generator< uknown, number, uknown > {
- yield new Promise( ( r ) => setTimeout( r, 1000 ) );
- return state.counter; // Now this is correctly inferred.
- },
- },
- } );
- ```
-
- That's it! Remember that the return type of a Generator is the second generic argument: `Generator< unknown, ReturnType, unknown >`.
-
-## Typing stores that are divided into multiple parts
-
-Sometimes, stores can be divided into different files. This can happen when different blocks share the same namespace, with each block loading the part of the store it needs.
-
-Let's look at an example of two blocks:
-
-- `todo-list`: A block that displays a list of todos.
-- `add-post-to-todo`: A block that shows a button to add a new todo item to the list with the text "Read {$post_title}".
-
-First, let's initialize the global and derived state of the `todo-list` block on the server.
-
-```php
- $todos,
- 'filter' => 'all',
- 'filteredTodos' => $todos,
-));
-?>
-
-
-```
-
-Now, let's type the server state and add the client store definition. Remember, `filteredTodos` is derived state, so you don't need to type it manually.
-
-```ts
-// todo-list-block/view.ts
-type ServerState = {
- state: {
- todos: string[];
- filter: 'all' | 'completed';
- };
-};
-
-const todoList = {
- state: {
- get filteredTodos(): string[] {
- return state.filter === 'completed'
- ? state.todos.filter( ( todo ) => todo.includes( '✅' ) )
- : state.todos;
- },
- },
- actions: {
- addTodo( todo: string ) {
- state.todos.push( todo );
- },
- },
-};
-
-// Merges the inferred types with the server state types.
-export type TodoList = ServerState & typeof todoList;
-
-// Injects the final types when calling the `store` function.
-const { state } = store< TodoList >( 'myTodoPlugin', todoList );
-```
-
-So far, so good. Now let's create our `add-post-to-todo` block.
-
-First, let's add the current post title to the server state.
-
-```php
- get_the_title(),
-));
-?>
-
-
-```
-
-Now, let's type that server state and add the client store definition.
-
-```ts
-// add-post-to-todo-block/view.ts
-type ServerState = {
- state: {
- postTitle: string;
- };
-};
-
-const addPostToTodo = {
- actions: {
- addPostToTodo() {
- const todo = `Read: ${ state.postTitle }`.trim();
- if ( ! state.todos.includes( todo ) ) {
- actions.addTodo( todo );
- }
- },
- },
-};
-
-// Merges the inferred types with the server state types.
-type Store = ServerState & typeof addPostToTodo;
-
-// Injects the final types when calling the `store` function.
-const { state, actions } = store< Store >( 'myTodoPlugin', addPostToTodo );
-```
-
-This works fine in the browser, but TypeScript will complain that, in this block, `state` and `actions` do not include `state.todos` and `actions.addtodo`.
-
-To fix this, we need to import the `TodoList` type from the `todo-list` block and merge it with the other types.
-
-```ts
-import type { TodoList } from '../todo-list-block/view';
-
-// ...
-
-// Merges the inferred types inferred the server state types.
-type Store = TodoList & ServerState & typeof addPostToTodo;
-```
-
-That's it! Now TypeScript will know that `state.todos` and `actions.addTodo` are available in the `add-post-to-todo` block.
-
-This approach allows the `add-post-to-todo` block to interact with the existing todo list while maintaining type safety and adding its own functionality to the shared store.
-
-If you need to use the `add-post-to-todo` types in the `todo-list` block, you simply have to export its types and import them in the other `view.ts` file.
-
-Finally, if you prefer to define all types manually instead of inferring them, you can define them in a separate file and import that definition into each of your store parts. Here's how you could do that for our todo list example:
-
-```ts
-// types.ts
-interface Store {
- state: {
- todos: string[];
- filter: 'all' | 'completed';
- filtered: string[];
- postTitle: string;
- };
- actions: {
- addTodo( todo: string ): void;
- addPostToTodo(): void;
- };
-}
-
-export default Store;
-```
-
-```ts
-// todo-list-block/view.ts
-import type Store from '../types';
-
-const { state } = store< Store >( 'myTodoPlugin', {
- // Everything is correctly typed here
-} );
-```
-
-```ts
-// add-post-to-todo-block/view.ts
-import type Store from '../types';
-
-const { state, actions } = store< Store >( 'myTodoPlugin', {
- // Everything is correctly typed here
-} );
-```
-
-This approach allows you to have full control over your types and ensures consistency across all parts of your store. It's particularly useful when you have a complex store structure or when you want to enforce a specific interface across multiple blocks or components.
-
-## Importing and exporting typed stores
-
-In the Interactivity API, stores from other namespaces can be accessed using the `store` function.
-
-Let's go back to our `todo-list` block example, but this time, let's imagine that the `add-post-to-todo` block belongs to a different plugin and therefore will use a different namespace.
-
-```ts
-// Import the store of the `todo-list` block.
-const myTodoPlugin = store( 'myTodoPlugin' );
-
-store( 'myAddPostToTodoPlugin', {
- actions: {
- addPostToTodo() {
- const todo = `Read: ${ state.postTitle }`.trim();
- if ( ! myTodoPlugin.state.todos.includes( todo ) ) {
- myTodoPlugin.actions.addTodo( todo );
- }
- },
- },
-} );
-```
-
-This works fine in the browser, but TypeScript will complain that `myTodoPlugin.state` and `myTodoPlugin.actions` are not typed.
-
-To fix that, the `myTodoPlugin` plugin can export the result of calling the `store` function with the correct types, and make that available using a script module.
-
-```ts
-// Export the already typed state and actions.
-export const { state, actions } = store< TodoList >( 'myTodoPlugin', {
- // ...
-} );
-```
-
-Now, the `add-post-to-todo` block can import the typed store from the `myTodoPlugin` script module, and it not only ensures that the store will be loaded, but that it also contains the correct types.
-
-```ts
-import { store } from '@wordpress/interactivity';
-import {
- state as todoState,
- actions as todoActions,
-} from 'my-todo-plugin-module';
-
-store( 'myAddPostToTodoPlugin', {
- actions: {
- addPostToTodo() {
- const todo = `Read: ${ state.postTitle }`.trim();
- if ( ! todoState.todos.includes( todo ) ) {
- todoActions.addTodo( todo );
- }
- },
- },
-} );
-```
-
-Remember that you will need to declare the `my-todo-plugin-module` script module as a dependency.
-
-If the other store is optional and you don't want to load it eagerly, a dynamic import can be used instead of a static import.
-
-```ts
-import { store } from '@wordpress/interactivity';
-
-store( 'myAddPostToTodoPlugin', {
- actions: {
- *addPostToTodo() {
- const todoPlugin = yield import( 'my-todo-plugin-module' );
- const todo = `Read: ${ state.postTitle }`.trim();
- if ( ! todoPlugin.state.todos.includes( todo ) ) {
- todoPlugin.actions.addTodo( todo );
- }
- },
- },
-} );
-```
-
-## Conclusion
-
-In this guide, we explored different approaches to typing the Interactivity API stores, from inferring types automatically to manually defining them. We also covered how to handle server-initialized state, local context, and derived state, as well as how to type asynchronous actions.
-
-Remember that the choice between inferring types and manually defining them depends on your specific needs and the complexity of your store. Whichever approach you choose, TypeScript will help you build better and more reliable interactive blocks.
diff --git a/docs/toc.json b/docs/toc.json
index 0d4689811b26ec..719ffa344e3744 100644
--- a/docs/toc.json
+++ b/docs/toc.json
@@ -214,9 +214,6 @@
},
{
"docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md": []
- },
- {
- "docs/reference-guides/interactivity-api/core-concepts/using-typescript.md": []
}
]
},
diff --git a/gutenberg.php b/gutenberg.php
index e15cb113ea65a1..8dddcfeccd5282 100644
--- a/gutenberg.php
+++ b/gutenberg.php
@@ -5,7 +5,7 @@
* Description: Printing since 1440. This is the development plugin for the block editor, site editor, and other future WordPress core functionality.
* Requires at least: 6.5
* Requires PHP: 7.2
- * Version: 19.3.0-rc.2
+ * Version: 19.3.0-rc.1
* Author: Gutenberg Team
* Text Domain: gutenberg
*
diff --git a/lib/client-assets.php b/lib/client-assets.php
index 2343530e5595a7..62e874d6b06c82 100644
--- a/lib/client-assets.php
+++ b/lib/client-assets.php
@@ -601,56 +601,6 @@ function gutenberg_register_vendor_scripts( $scripts ) {
}
add_action( 'wp_default_scripts', 'gutenberg_register_vendor_scripts' );
-/**
- * Registers or re-registers Gutenberg Script Modules.
- *
- * Script modules that are registered by Core will be re-registered by Gutenberg.
- *
- * @since 19.3.0
- */
-function gutenberg_default_script_modules() {
- /*
- * Expects multidimensional array like:
- *
- * 'interactivity/index.min.js' => array('dependencies' => array(…), 'version' => '…'),
- * 'interactivity/debug.min.js' => array('dependencies' => array(…), 'version' => '…'),
- * 'interactivity-router/index.min.js' => …
- */
- $assets = include gutenberg_dir_path() . '/build-module/assets.php';
-
- foreach ( $assets as $file_name => $script_module_data ) {
- /*
- * Build the WordPress Script Module ID from the file name.
- * Prepend `@wordpress/` and remove extensions and `/index` if present:
- * - interactivity/index.min.js => @wordpress/interactivity
- * - interactivity/debug.min.js => @wordpress/interactivity/debug
- * - block-library/query/view.js => @wordpress/block-library/query/view
- */
- $script_module_id = '@wordpress/' . preg_replace( '~(?:/index)?\.min\.js$~D', '', $file_name, 1 );
- switch ( $script_module_id ) {
- /*
- * Interactivity exposes two entrypoints, "/index" and "/debug".
- * "/debug" should replalce "/index" in devlopment.
- */
- case '@wordpress/interactivity/debug':
- if ( ! SCRIPT_DEBUG ) {
- continue 2;
- }
- $script_module_id = '@wordpress/interactivity';
- break;
- case '@wordpress/interactivity':
- if ( SCRIPT_DEBUG ) {
- continue 2;
- }
- break;
- }
-
- $path = gutenberg_url( "build-module/{$file_name}" );
- wp_register_script_module( $script_module_id, $path, $script_module_data['dependencies'], $script_module_data['version'] );
- }
-}
-remove_action( 'wp_default_scripts', 'wp_default_script_modules' );
-add_action( 'wp_default_scripts', 'gutenberg_default_script_modules' );
/*
* Always remove the Core action hook while gutenberg_enqueue_stored_styles() exists to avoid styles being printed twice.
diff --git a/lib/experimental/script-modules.php b/lib/experimental/script-modules.php
index fe23786fc03621..f65bc1704dd890 100644
--- a/lib/experimental/script-modules.php
+++ b/lib/experimental/script-modules.php
@@ -239,5 +239,26 @@ function gutenberg_a11y_script_module_html() {
. ''
. '';
}
-add_action( 'wp_footer', 'gutenberg_a11y_script_module_html' );
-add_action( 'admin_footer', 'gutenberg_a11y_script_module_html' );
+
+/**
+ * Registers Gutenberg Script Modules.
+ *
+ * @since 19.3
+ */
+function gutenberg_register_script_modules() {
+ // When in production, use the plugin's version as the default asset version;
+ // else (for development or test) default to use the current time.
+ $default_version = defined( 'GUTENBERG_VERSION' ) && ! SCRIPT_DEBUG ? GUTENBERG_VERSION : time();
+
+ wp_deregister_script_module( '@wordpress/a11y' );
+ wp_register_script_module(
+ '@wordpress/a11y',
+ gutenberg_url( 'build-module/a11y/index.min.js' ),
+ array(),
+ $default_version
+ );
+
+ add_action( 'wp_footer', 'gutenberg_a11y_script_module_html' );
+ add_action( 'admin_footer', 'gutenberg_a11y_script_module_html' );
+}
+add_action( 'init', 'gutenberg_register_script_modules' );
diff --git a/lib/interactivity-api.php b/lib/interactivity-api.php
index ff68936f054a7e..c00d68bc70e8e2 100644
--- a/lib/interactivity-api.php
+++ b/lib/interactivity-api.php
@@ -5,6 +5,37 @@
* @package gutenberg
*/
+/**
+ * Deregisters the Core Interactivity API Modules and replace them
+ * with the ones from the Gutenberg plugin.
+ */
+function gutenberg_reregister_interactivity_script_modules() {
+ $default_version = defined( 'GUTENBERG_VERSION' ) && ! SCRIPT_DEBUG ? GUTENBERG_VERSION : time();
+ wp_deregister_script_module( '@wordpress/interactivity' );
+ wp_deregister_script_module( '@wordpress/interactivity-router' );
+
+ wp_register_script_module(
+ '@wordpress/interactivity',
+ gutenberg_url( '/build-module/' . ( SCRIPT_DEBUG ? 'interactivity/debug.min.js' : 'interactivity/index.min.js' ) ),
+ array(),
+ $default_version
+ );
+
+ wp_register_script_module(
+ '@wordpress/interactivity-router',
+ gutenberg_url( '/build-module/interactivity-router/index.min.js' ),
+ array(
+ array(
+ 'id' => '@wordpress/a11y',
+ 'import' => 'dynamic',
+ ),
+ '@wordpress/interactivity',
+ ),
+ $default_version
+ );
+}
+add_action( 'init', 'gutenberg_reregister_interactivity_script_modules' );
+
/**
* Adds script data to the interactivity-router script module.
*
diff --git a/packages/babel-preset-default/CHANGELOG.md b/packages/babel-preset-default/CHANGELOG.md
index b31be6ffd8d56d..c8c3fdb66ecb0e 100644
--- a/packages/babel-preset-default/CHANGELOG.md
+++ b/packages/babel-preset-default/CHANGELOG.md
@@ -1,16 +1,8 @@
-## Unreleased
+## Internal
-### Bug Fixes
-
-- Fix a bug in 8.8.1 due to missing files in the published package ([#65481](https://github.com/WordPress/gutenberg/pull/65481)).
-
-## 8.8.0 (2024-09-19)
-
-### Internal
-
-- Added `addPolyfillComments` option. When used, it will automatically add magic comments to mark files that need `wp-polyfill` ([#65292](https://github.com/WordPress/gutenberg/pull/65292)).
+- Added `addPolyfillComments` option. When used, it will automatically add magic comments to mark files that need `wp-polyfill`.
## 8.7.0 (2024-09-05)
diff --git a/packages/babel-preset-default/package.json b/packages/babel-preset-default/package.json
index 1203586ec20292..f0f015cb2203f7 100644
--- a/packages/babel-preset-default/package.json
+++ b/packages/babel-preset-default/package.json
@@ -26,9 +26,7 @@
},
"files": [
"build",
- "index.js",
- "polyfill-exclusions.js",
- "replace-polyfills.js"
+ "index.js"
],
"main": "index.js",
"dependencies": {
diff --git a/packages/base-styles/_z-index.scss b/packages/base-styles/_z-index.scss
index 77238c6f386084..cc99df6dbeaafc 100644
--- a/packages/base-styles/_z-index.scss
+++ b/packages/base-styles/_z-index.scss
@@ -8,6 +8,7 @@ $z-layers: (
".block-editor-block-switcher__arrow": 1,
".block-editor-block-list__block {core/image aligned wide or fullwide}": 20,
".block-library-classic__toolbar": 31, // When scrolled to top this toolbar needs to sit over block-editor-block-toolbar
+ ".block-editor-block-list__block-selection-button": 22,
".components-form-toggle__input": 1,
".editor-text-editor__toolbar": 1,
@@ -69,6 +70,10 @@ $z-layers: (
// Below the media library backdrop (.media-modal-backdrop), which has a z-index of 159900.
".block-editor-global-styles-background-panel__popover": 159900 - 10,
+ // Small screen inner blocks overlay must be displayed above drop zone,
+ // settings menu, and movers.
+ ".block-editor-block-list__layout.has-overlay::after": 60,
+
// The toolbar, when contextual, should be above any adjacent nested block click overlays.
".block-editor-block-contextual-toolbar": 61,
diff --git a/packages/block-editor/README.md b/packages/block-editor/README.md
index 75d7e8879572d4..a474d1df7e56d0 100644
--- a/packages/block-editor/README.md
+++ b/packages/block-editor/README.md
@@ -1027,11 +1027,11 @@ _Parameters_
### useZoomOut
-A hook used to set the zoomed out view, invoking the hook sets the mode.
+A hook used to set the editor mode to zoomed out mode, invoking the hook sets the mode.
_Parameters_
-- _zoomOut_ `boolean`: If we should zoom out or not.
+- _zoomOut_ `boolean`: If we should enter into zoomOut mode or not
### Warning
diff --git a/packages/block-editor/src/components/block-actions/index.js b/packages/block-editor/src/components/block-actions/index.js
index f06c8addedad50..5e12165c679424 100644
--- a/packages/block-editor/src/components/block-actions/index.js
+++ b/packages/block-editor/src/components/block-actions/index.js
@@ -29,6 +29,7 @@ export default function BlockActions( {
getBlockRootClientId,
getBlocksByClientId,
getDirectInsertBlock,
+ canMoveBlocks,
canRemoveBlocks,
} = select( blockEditorStore );
@@ -43,6 +44,7 @@ export default function BlockActions( {
: null;
return {
+ canMove: canMoveBlocks( clientIds ),
canRemove: canRemoveBlocks( clientIds ),
canInsertBlock: canInsertDefaultBlock || !! directInsertBlock,
canCopyStyles: blocks.every( ( block ) => {
@@ -65,7 +67,8 @@ export default function BlockActions( {
);
const { getBlocksByClientId, getBlocks } = useSelect( blockEditorStore );
- const { canRemove, canInsertBlock, canCopyStyles, canDuplicate } = selected;
+ const { canMove, canRemove, canInsertBlock, canCopyStyles, canDuplicate } =
+ selected;
const {
removeBlocks,
@@ -74,6 +77,9 @@ export default function BlockActions( {
insertAfterBlock,
insertBeforeBlock,
flashBlock,
+ setBlockMovingClientId,
+ setNavigationMode,
+ selectBlock,
} = useDispatch( blockEditorStore );
const notifyCopy = useNotifyCopy();
@@ -83,6 +89,7 @@ export default function BlockActions( {
canCopyStyles,
canDuplicate,
canInsertBlock,
+ canMove,
canRemove,
onDuplicate() {
return duplicateBlocks( clientIds, updateSelection );
@@ -96,6 +103,11 @@ export default function BlockActions( {
onInsertAfter() {
insertAfterBlock( clientIds[ clientIds.length - 1 ] );
},
+ onMoveTo() {
+ setNavigationMode( true );
+ selectBlock( clientIds[ 0 ] );
+ setBlockMovingClientId( clientIds[ 0 ] );
+ },
onGroup() {
if ( ! clientIds.length ) {
return;
diff --git a/packages/block-editor/src/components/block-controls/use-has-block-controls.js b/packages/block-editor/src/components/block-controls/use-has-block-controls.js
new file mode 100644
index 00000000000000..f7884cc1882ed5
--- /dev/null
+++ b/packages/block-editor/src/components/block-controls/use-has-block-controls.js
@@ -0,0 +1,35 @@
+/**
+ * WordPress dependencies
+ */
+import { __experimentalUseSlotFills as useSlotFills } from '@wordpress/components';
+import warning from '@wordpress/warning';
+
+/**
+ * Internal dependencies
+ */
+import groups from './groups';
+
+export function useHasAnyBlockControls() {
+ let hasAnyBlockControls = false;
+ for ( const group in groups ) {
+ // It is safe to violate the rules of hooks here as the `groups` object
+ // is static and will not change length between renders. Do not return
+ // early as that will cause the hook to be called a different number of
+ // times between renders.
+ // eslint-disable-next-line react-hooks/rules-of-hooks
+ if ( useHasBlockControls( group ) ) {
+ hasAnyBlockControls = true;
+ }
+ }
+ return hasAnyBlockControls;
+}
+
+export function useHasBlockControls( group = 'default' ) {
+ const Slot = groups[ group ]?.Slot;
+ const fills = useSlotFills( Slot?.__unstableName );
+ if ( ! Slot ) {
+ warning( `Unknown BlockControls group "${ group }" provided.` );
+ return null;
+ }
+ return !! fills?.length;
+}
diff --git a/packages/block-editor/src/components/block-inspector/index.js b/packages/block-editor/src/components/block-inspector/index.js
index 475d4f6a4b8c2e..a18556f2fa5bd9 100644
--- a/packages/block-editor/src/components/block-inspector/index.js
+++ b/packages/block-editor/src/components/block-inspector/index.js
@@ -40,36 +40,83 @@ function BlockStylesPanel( { clientId } ) {
);
}
+function BlockInspectorLockedBlocks( { topLevelLockedBlock } ) {
+ const contentClientIds = useSelect(
+ ( select ) => {
+ const {
+ getClientIdsOfDescendants,
+ getBlockName,
+ getBlockEditingMode,
+ } = select( blockEditorStore );
+ return getClientIdsOfDescendants( topLevelLockedBlock ).filter(
+ ( clientId ) =>
+ getBlockName( clientId ) !== 'core/list-item' &&
+ getBlockEditingMode( clientId ) === 'contentOnly'
+ );
+ },
+ [ topLevelLockedBlock ]
+ );
+ const hasBlockStyles = useSelect(
+ ( select ) => {
+ const { getBlockName } = select( blockEditorStore );
+ const { getBlockStyles } = select( blocksStore );
+ return !! getBlockStyles( getBlockName( topLevelLockedBlock ) )
+ ?.length;
+ },
+ [ topLevelLockedBlock ]
+ );
+ const blockInformation = useBlockDisplayInformation( topLevelLockedBlock );
+ return (
+