Backports for 6.6 Beta/RC

[ellatrix]

This issue supersedes #61226. See Back-merging code to WordPress Core.

I'm starting a new issue because I'd like to try a new approach based on the backport log. Note that, since we started the backport log before Beta, this will also include backports from before Beta.

PRs have title/status previews, so it's easy to have an overview of overall status (no need for a checklist).

• add support for __experimentalSkiSerialization to the shadow attribute wordpress-develop#6279
  • Shadow: add unit tests for shadow support #60063
• Reduce specificity of global styles and layout selectors. wordpress-develop#6522
  • Try reducing specificity of global styles selectors only. #60106
  • Try reducing specificity of layout style selectors #60228
  • Styles: try wrapping with :root to fix reset styles #61638
• Backport: Templates perf: resolve patterns server side wordpress-develop#6559
  • Templates perf: resolve patterns server side #60349
  • Patterns: guard for unknown pattern in server-side resolver #60464
  • Add null check to prevent errors in get_block_template filter #60491
  • Templates: only resolve patterns for REST API endpoints #61757
• Add aspect ratio presets support via theme.json wordpress-develop#6567
  • Add aspect ratio presets support via theme.json #47271
  • fix make dimensions.aspectRatios key of theme.json files translatable #61774
• Add new textAlign block support wordpress-develop#6590
  • Try: Add new textAlign block support #59531
  • Fix: Enable Text Align UI to be controlled correctly with theme.json #61182
  • Global Styles: Add block-level Text Alignment UI #61717
• Toolbar: Update the site editor link in the Admin Bar wordpress-develop#6605
  • Fix the site editor Admin Bar menu item #61851
• Backport theme.json version 3 migrations wordpress-develop#6616
  • Add defaultFontSizes theme.json (theme.json v3) #58409
  • Fix WP versions for theme.json v3 migration in inline docs #61328
  • Add defaultSpacingSizes option (theme.json v3) #61842
  • Fix UI order for theme.json spacing sizes #62199
  • Add default-spacing-sizes and default-font-sizes options for classic themes #62252
• Improve consistency of root padding. wordpress-develop#6656
  • More consistent root padding #60715
• Block Styles: Extend block style variations as mechanism for achieving section styling wordpress-develop#6662
  • Block Styles: Extend block style variations as mechanism for achieving section styling #57908
  • Block Styles: Fix block style variation styles for blocks with complex selectors #62125
• Add handling for __default attribute to block bindings for pattern overrides wordpress-develop#6694
  • Add __default binding for pattern overrides #60694
• Global styles code quality refactoring wordpress-develop#6731
  • Global styles code quality refactoring #62299
• Editor: code quality improvements for theme.json migrate API wordpress-develop#6737
  • Migrate theme.json based on origin #62305
• Revert changes to block bindings replacement logic and stop using regex wordpress-develop#6744
  • Revert changes to bindings replacement logic to not use regex #62355
• Update: register block style variations defined by the theme using the init action wordpress-develop#6756
  • Section Styles: Register block style variations on init #62461
  • Global Styles: Fix registration of theme style variation defined block styles #62495
• Spell JavaScript in accordance with the word mark. wordpress-develop#6785
  • Use wordmarks dangit (GitHub, JavaScript) #62459
• Fix block style variation custom CSS output on the front end wordpress-develop#6797
  • Add custom CSS for block style variations. #62526
• Section Styles: Add slug to solve inconsistency in variation names wordpress-develop#6824
  • Section styles: consolidate variation name #62550
• Theme JSON: Add missing i18n for variations wordpress-develop#6825
  • Section styles: support i18n for variations declared in theme.json or theme style variations #62552
• Global Styles: Prevent duplicate CSS for block style variations wordpress-develop#6827
  • Global Styles: Prevent duplicate block style variations CSS #62465
• Global Styles: Avoid unnecessary processing of theme.json variation partials wordpress-develop#6837
  • Global Styles: Skip registration of variation styles when unsupported #62529
  • Global Styles: Add style variation partial cache #62610
• Correct documentation for WP_Block_Parser_Frame class wordpress-develop#6841
  • Correct documentation for WP_Block_Parser_Frame class #62598
• Do not use init to register block style variations defined via theme.json wordpress-develop#6844
  • Section Styles: Switch away from using init for variation registration #62640
• Allow children of alignfull flow layouts to have root padding. wordpress-develop#6854
  • Allow children of alignfull flow layouts to have root padding. #62670
• Add: Template and template_lock to post types endpoint. wordpress-develop#6864
  • Fix: Post_type template is not used when creating a page in site editor. #62488
  • Update: Followups to the template and template_lock rest api addition. #62696
• Section Styles: improve performance and conceptual consistency wordpress-develop#6873
  • Section Styles: improve performance and conceptual consistency #62712
• Section Styles: Prevent flash of variation style updates wordpress-develop#6959
  • Section Styles: Prevent flash of variation styles in post editor #63071
• Fix root padding for alignwide blocks. wordpress-develop#6987
  • Include alignwide in nested has-outer-padding logic #63207
• Section Styles: Fix ref values within block style variations wordpress-develop#6989
  • Section Styles: Resolve ref values in variations data #63172

[bgardner]

@ellatrix Any idea when the issues on this list will get backported to 6.6 Beta? (Asking in particular about #62199 and if it can get into Beta 2.)

That issue is holding me up from doing extensive testing with 6.6 Beta, as I cannot right now because of the spacing issues.

[ellatrix]

@bgardner It's already been backported in WordPress/wordpress-develop#6616, it's in the list above

[bgardner]

@ellatrix Great, that’s what I thought. Hoping it makes it into Beta 2. 🙏

[spacedmonkey]

@ellatrix Am I good to backport #62522. I have a PR WordPress/wordpress-develop#6895.

[ellatrix]

Of course, please do