prep build 07/04

.eslintrc.js

@@ -397,6 +397,7 @@ module.exports = {
 				'no-restricted-syntax': [
 					'error',
 					...restrictedSyntax,
+					...restrictedSyntaxComponents,
 					{
 						selector:
 							':matches(Literal[value=/--wp-admin-theme-/],TemplateElement[value.cooked=/--wp-admin-theme-/])',

.github/CODEOWNERS

@@ -119,9 +119,9 @@
 /packages/plugins                               @gziolo @adamsilverstein
 
 # Rich Text
-/packages/format-library                        @ellatrix @fluiddot @dcalhoun
-/packages/rich-text                             @ellatrix @fluiddot @dcalhoun
-/packages/block-editor/src/components/rich-text @ellatrix @fluiddot @dcalhoun
+/packages/format-library                        @ellatrix @dcalhoun
+/packages/rich-text                             @ellatrix @dcalhoun
+/packages/block-editor/src/components/rich-text @ellatrix @dcalhoun
 
 # Project Management
 /.github                                        @desrosj

backport-changelog/6.6/6959.md

@@ -0,0 +1,4 @@
+https://github.com/WordPress/wordpress-develop/pull/6959
+
+* https://github.com/WordPress/gutenberg/pull/63071
+

changelog.txt

@@ -1,5 +1,25 @@
 == Changelog ==
 
+= 18.7.1 =
+
+
+## Changelog
+
+### Bug Fixes
+
+#### Block Library
+- Button Block: Add back compat for WP6.4 regarding HTML Tag Processor. ([63082](https://github.com/WordPress/gutenberg/pull/63082))
+
+
+
+
+## Contributors
+
+The following contributors merged PRs in this release:
+
+@t-hamano
+
+
 = 18.7.0 =
 
 ## Changelog

docs/reference-guides/block-api/block-metadata.md

@@ -745,7 +745,7 @@ $metadata = array(
 );
 ```
 
-Implementation follows the existing [get_plugin_data](https://codex.wordpress.org/Function_Reference/get_plugin_data) function which parses the plugin contents to retrieve the plugin’s metadata, and it applies translations dynamically.
+Implementation follows the existing [get_plugin_data](https://developer.wordpress.org/reference/functions/get_plugin_data) function which parses the plugin contents to retrieve the plugin’s metadata, and it applies translations dynamically.
 
 ### JavaScript
 

docs/reference-guides/core-blocks.md

@@ -426,7 +426,7 @@ Create a list item. ([Source](https://github.com/WordPress/gutenberg/tree/trunk/
 -	**Category:** text
 -	**Parent:** core/list
 -	**Allowed Blocks:** core/list
--	**Supports:** interactivity (clientNavigation), spacing (margin, padding), splitting, typography (fontSize, lineHeight), ~~className~~
+-	**Supports:** color (background, gradients, link, text), interactivity (clientNavigation), spacing (margin, padding), splitting, typography (fontSize, lineHeight), ~~className~~
 -	**Attributes:** content, placeholder
 
 ## Login/out

docs/reference-guides/data/data-core.md

@@ -790,7 +790,7 @@ _Parameters_
 -   _kind_ `string`: Kind of the entity.
 -   _name_ `string`: Name of the entity.
 -   _recordId_ `Object`: ID of the record.
--   _options_ `Object`: Saving options.
+-   _options_ `Object=`: Saving options.
 
 ### saveEntityRecord
 

docs/reference-guides/filters/README.md

@@ -4,4 +4,4 @@
 
 There are two types of hooks: [Actions](https://developer.wordpress.org/plugins/hooks/actions/) and [Filters](https://developer.wordpress.org/plugins/hooks/filters/). In addition to PHP actions and filters, WordPress also provides a mechanism for registering and executing hooks in JavaScript. This functionality is also available on npm as the [@wordpress/hooks](https://www.npmjs.com/package/@wordpress/hooks) package, for general purpose use.
 
-You can also learn more about both APIs: [PHP](https://codex.wordpress.org/Plugin_API/) and [JavaScript](/packages/hooks/README.md).
+You can also learn more about both APIs: [PHP](https://developer.wordpress.org/reference/) and [JavaScript](/packages/hooks/README.md).

docs/reference-guides/interactivity-api/README.md

@@ -101,9 +101,12 @@ Here you have some more resources to learn/read more about the Interactivity API
 - [WordPress 6.5 Dev Note](https://make.wordpress.org/core/2024/03/04/interactivity-api-dev-note/)
 - [Merge announcement](https://make.wordpress.org/core/2024/02/19/merge-announcement-interactivity-api/)
 - [Proposal: The Interactivity API – A better developer experience in building interactive blocks](https://make.wordpress.org/core/2023/03/30/proposal-the-interactivity-api-a-better-developer-experience-in-building-interactive-blocks/)
-- [Interactivity API Discussions](https://github.com/WordPress/gutenberg/discussions/52882)
-- Developer Hours sessions ([Americas](https://www.youtube.com/watch?v=RXNoyP2ZiS8&t=664s) & [APAC/EMEA](https://www.youtube.com/watch?v=6ghbrhyAcvA))
+- [Interactivity API Discussions](https://github.com/WordPress/gutenberg/discussions/52882), especially the [showcase](https://github.com/WordPress/gutenberg/discussions/55642#discussioncomment-9667164) discussions.   
 - [wpmovies.dev](http://wpmovies.dev/) demo and its [wp-movies-demo](https://github.com/WordPress/wp-movies-demo) repo
+- Examples using the Interactivity API at [block-development-examples](https://github.com/WordPress/block-development-examples):
+  - [`interactivity-api-block-833d15`](https://github.com/WordPress/block-development-examples/tree/trunk/plugins/833d15)
+  - [`interactivity-api-countdown-3cd73e`](https://github.com/WordPress/block-development-examples/tree/trunk/plugins/interactivity-api-countdown-3cd73e)
+  - [`interactivity-api-quiz-1835fa`](https://github.com/WordPress/block-development-examples/tree/trunk/plugins/interactivity-api-quiz-1835fa)
 
 <div class="callout">
     There's a Tracking Issue opened to ease the coordination of the work related to the Interactivity API Docs: <a href="https://github.com/WordPress/gutenberg/issues/53296">Documentation for the Interactivity API - Tracking Issue #53296</a>

docs/reference-guides/interactivity-api/iapi-quick-start-guide.md

@@ -39,3 +39,15 @@ npx @wp-now/wp-now start
 ```
 
 You should be able to insert the "My First Interactive Block" block into any post and see how it behaves in the front end when published.
+
+<div class="callout callout-info">
+    <p>To get more advanced examples of using the Interactivity API you can check the following resources:</p>
+    <ul>
+      <li><a href="https://developer.wordpress.org/block-editor/reference-guides/interactivity-api/#docs-examples">Docs & Examples</a></li>
+      <li><a href="https://github.com/WordPress/gutenberg/discussions/52894">Getting Started - and other learning resources</a></li>
+      <li><a href="https://github.com/WordPress/gutenberg/discussions/55642#">Interactivity API showcase</a></li>
+    </ul>
+</div>
+
+
+

lib/compat/wordpress-6.4/html-api/class-gutenberg-html-tag-processor-6-4.php

@@ -2031,8 +2031,8 @@ public function set_attribute( $name, $value ) {
 		 *
 		 * @see https://html.spec.whatwg.org/#attributes-2
 		 *
-		 * @todo As the only regex pattern maybe we should take it out?
-		 *       Are Unicode patterns available broadly in Core?
+		 * @TODO as the only regex pattern maybe we should take it out? are
+		 *       Unicode patterns available broadly in Core?
 		 */
 		if ( preg_match(
 			'~[' .
@@ -2071,7 +2071,14 @@ public function set_attribute( $name, $value ) {
 		if ( true === $value ) {
 			$updated_attribute = $name;
 		} else {
-			$escaped_new_value = esc_attr( $value );
+			$comparable_name = strtolower( $name );
+
+			/*
+			 * Escape URL attributes.
+			 *
+			 * @see https://html.spec.whatwg.org/#attributes-3
+			 */
+			$escaped_new_value = in_array( $comparable_name, wp_kses_uri_attributes() ) ? esc_url( $value ) : esc_attr( $value );
 			$updated_attribute = "{$name}=\"{$escaped_new_value}\"";
 		}
 

lib/compat/wordpress-6.4/html-api/class-wp-html-active-formatting-elements.php

@@ -99,16 +99,16 @@ public function current_node() {
 		 */
 		public function push( $token ) {
 			/*
-			* > If there are already three elements in the list of active formatting elements after the last marker,
-			* > if any, or anywhere in the list if there are no markers, that have the same tag name, namespace, and
-			* > attributes as element, then remove the earliest such element from the list of active formatting
-			* > elements. For these purposes, the attributes must be compared as they were when the elements were
-			* > created by the parser; two elements have the same attributes if all their parsed attributes can be
-			* > paired such that the two attributes in each pair have identical names, namespaces, and values
-			* > (the order of the attributes does not matter).
-			*
-			* @todo Implement the "Noah's Ark clause" to only add up to three of any given kind of formatting elements to the stack.
-			*/
+			 * > If there are already three elements in the list of active formatting elements after the last marker,
+			 * > if any, or anywhere in the list if there are no markers, that have the same tag name, namespace, and
+			 * > attributes as element, then remove the earliest such element from the list of active formatting
+			 * > elements. For these purposes, the attributes must be compared as they were when the elements were
+			 * > created by the parser; two elements have the same attributes if all their parsed attributes can be
+			 * > paired such that the two attributes in each pair have identical names, namespaces, and values
+			 * > (the order of the attributes does not matter).
+			 *
+			 * @TODO: Implement the "Noah's Ark clause" to only add up to three of any given kind of formatting elements to the stack.
+			 */
 			// > Add element to the list of active formatting elements.
 			$this->stack[] = $token;
 		}

lib/compat/wordpress-6.4/html-api/class-wp-html-open-elements.php

@@ -112,7 +112,7 @@ public function current_node() {
 		 * @param string[] $termination_list List of elements that terminate the search.
 		 * @return bool Whether the element was found in a specific scope.
 		 */
-		public function has_element_in_specific_scope( $tag_name, $termination_list ) { // phpcs:ignore VariableAnalysis.CodeAnalysis.VariableAnalysis.UnusedVariable
+		public function has_element_in_specific_scope( $tag_name, $termination_list ) {
 			foreach ( $this->walk_up() as $node ) {
 				if ( $node->node_name === $tag_name ) {
 					return true;
@@ -147,12 +147,12 @@ public function has_element_in_scope( $tag_name ) {
 				array(
 
 					/*
-					* Because it's not currently possible to encounter
-					* one of the termination elements, they don't need
-					* to be listed here. If they were, they would be
-					* unreachable and only waste CPU cycles while
-					* scanning through HTML.
-					*/
+					 * Because it's not currently possible to encounter
+					 * one of the termination elements, they don't need
+					 * to be listed here. If they were, they would be
+					 * unreachable and only waste CPU cycles while
+					 * scanning through HTML.
+					 */
 				)
 			);
 		}
@@ -169,7 +169,7 @@ public function has_element_in_scope( $tag_name ) {
 		 * @param string $tag_name Name of tag to check.
 		 * @return bool Whether given element is in scope.
 		 */
-		public function has_element_in_list_item_scope( $tag_name ) { // phpcs:ignore VariableAnalysis.CodeAnalysis.VariableAnalysis.UnusedVariable
+		public function has_element_in_list_item_scope( $tag_name ) {
 			throw new WP_HTML_Unsupported_Exception( 'Cannot process elements depending on list item scope.' );
 
 			return false; // The linter requires this unreachable code until the function is implemented and can return.
@@ -201,7 +201,7 @@ public function has_element_in_button_scope( $tag_name ) {
 		 * @param string $tag_name Name of tag to check.
 		 * @return bool Whether given element is in scope.
 		 */
-		public function has_element_in_table_scope( $tag_name ) { // phpcs:ignore VariableAnalysis.CodeAnalysis.VariableAnalysis.UnusedVariable
+		public function has_element_in_table_scope( $tag_name ) {
 			throw new WP_HTML_Unsupported_Exception( 'Cannot process elements depending on table scope.' );
 
 			return false; // The linter requires this unreachable code until the function is implemented and can return.
@@ -219,7 +219,7 @@ public function has_element_in_table_scope( $tag_name ) { // phpcs:ignore Variab
 		 * @param string $tag_name Name of tag to check.
 		 * @return bool Whether given element is in scope.
 		 */
-		public function has_element_in_select_scope( $tag_name ) { // phpcs:ignore VariableAnalysis.CodeAnalysis.VariableAnalysis.UnusedVariable
+		public function has_element_in_select_scope( $tag_name ) {
 			throw new WP_HTML_Unsupported_Exception( 'Cannot process elements depending on select scope.' );
 
 			return false; // The linter requires this unreachable code until the function is implemented and can return.
@@ -371,8 +371,8 @@ public function walk_up() {
 		}
 
 		/*
-		* Internal helpers.
-		*/
+		 * Internal helpers.
+		 */
 
 		/**
 		 * Updates internal flags after adding an element.
@@ -389,9 +389,9 @@ public function walk_up() {
 		 */
 		public function after_element_push( $item ) {
 			/*
-			* When adding support for new elements, expand this switch to trap
-			* cases where the precalculated value needs to change.
-			*/
+			 * When adding support for new elements, expand this switch to trap
+			 * cases where the precalculated value needs to change.
+			 */
 			switch ( $item->node_name ) {
 				case 'BUTTON':
 					$this->has_p_in_button_scope = false;
@@ -418,9 +418,9 @@ public function after_element_push( $item ) {
 		 */
 		public function after_element_pop( $item ) {
 			/*
-			* When adding support for new elements, expand this switch to trap
-			* cases where the precalculated value needs to change.
-			*/
+			 * When adding support for new elements, expand this switch to trap
+			 * cases where the precalculated value needs to change.
+			 */
 			switch ( $item->node_name ) {
 				case 'BUTTON':
 					$this->has_p_in_button_scope = $this->has_element_in_button_scope( 'P' );

lib/compat/wordpress-6.4/html-api/class-wp-html-processor-state.php

@@ -23,19 +23,19 @@
 	 */
 	class WP_HTML_Processor_State {
 		/*
-		* Insertion mode constants.
-		*
-		* These constants exist and are named to make it easier to
-		* discover and recognize the supported insertion modes in
-		* the parser.
-		*
-		* Out of all the possible insertion modes, only those
-		* supported by the parser are listed here. As support
-		* is added to the parser for more modes, add them here
-		* following the same naming and value pattern.
-		*
-		* @see https://html.spec.whatwg.org/#the-insertion-mode
-		*/
+		 * Insertion mode constants.
+		 *
+		 * These constants exist and are named to make it easier to
+		 * discover and recognize the supported insertion modes in
+		 * the parser.
+		 *
+		 * Out of all the possible insertion modes, only those
+		 * supported by the parser are listed here. As support
+		 * is added to the parser for more modes, add them here
+		 * following the same naming and value pattern.
+		 *
+		 * @see https://html.spec.whatwg.org/#the-insertion-mode
+		 */
 
 		/**
 		 * Initial insertion mode for full HTML parser.
@@ -87,6 +87,15 @@ class WP_HTML_Processor_State {
 		 */
 		public $active_formatting_elements = null;
 
+		/**
+		 * Refers to the currently-matched tag, if any.
+		 *
+		 * @since 6.4.0
+		 *
+		 * @var WP_HTML_Token|null
+		 */
+		public $current_token = null;
+
 		/**
 		 * Tree construction insertion mode.
 		 *