6.1 Product Walk-Through

This summary post provides information regarding the forthcoming live stream walk-through preview of WordPress 6.1. 

Date, Time, and Location

The event will take place on Tuesday, September 13, 2022 at 04:00 PM UTC via Zoom. Please note that the Zoom link will be provided closer to the date of this event. The event will be recorded and archived for on-demand viewing.

Overview

WordPress 6.1 release squad members will join contributors from #core and the broader WordPress community to conduct an informal preview of the major features in the upcoming release. This Zoom event will include discussion on the new features, resolved tickets, potential blockers, and other topics in a live, public manner.

After the success of the inaugural 6.0 walk-through, this and future releases can expect to see this as a new part of the release cycle.

It’s a fun and simple way to bring more people from the community into the release cycle activities, and preview elements from the upcoming release ahead of the release date. It is also an excellent opportunity to foster open and transparent communication and connect various members, groups, and stakeholders from the WordPress community. 

Participants

Event attendance is open to the general public, and it will be recorded. 

The 6.1 walk-through panel will be composed of a moderator to help guide the conversation among a subset of the WordPress 6.1 release squad members:

Together the panelists will demo features and discuss some of what’s to come in the 6.1 release. The presenters will also answer questions related to the release from attendees if time allows. The recording as well as all questions will be collected and addressed in a follow-up summary post.

For More Information

Please feel free to ask questions about the event’s logistics as replies/comments on this post. If you would like to submit a question ahead of time to be considered for discussion during the event, please share your question in the Make WordPress Slack within the #walkthrough channel.

#6-1, #releases 

Props to all the participants for volunteering, as well as @priethor, @desrosj, @cbringmann, @rmartinezduque, and @dansoschin for helping prepare this announcement and general walk-through readiness.

Editor chat agenda – 7th September 2022

Facilitator and notetaker: @get_dave.

This is the agenda for the weekly editor chat scheduled for Wednesday, September 7, 2022 at 02:00 PM UTC.

This meeting is held in the #core-editor channel in the Making WordPress Slack.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

X-post: Improving DevHub Code References

X-post from +make.wordpress.org/meta: Improving DevHub Code References

Performance Chat Agenda: 6 September 2022

Here is the agenda for next week’s performance team meeting scheduled for Tuesday, September 6, 2022 at 03:00 PM UTC.


This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack

#agenda, #meeting, #performance, #performance-chat

Dev Chat Summary, August 31, 2022

1. Welcome and introduction

The start of the weekly WordPress developers chat meeting in the Core team channel can be found at this Slack thread.

Meeting agenda preparation and facilitation: @webcommsat and @marybaum. Thanks to everyone who sent in materials or shared tickets.

Meeting summary: @webcommsat. Review: @marybaum, @costdev.

References: Contributor Handbook. Purpose and role of weekly Dev Chat, held on Wednesdays at 20:00 UTC.

2. Announcements

@bph: The Gutenberg 14.0 is in the repo, and a Make Core post is in progress. The performance tests need another look. Props to @desrosj for getting it over the finish line and release lead @onemaggie. Post dev chat – What’s new in Gutenberg 14.01.

3. Blogs posts

Core editor improvement: refining the template creation experience (August 25, 2022)

Post dev chat: A Week in Core (August 31, 2022) thanks to @audrasjb.

4. Upcoming releases

a) The next major is 6.1.

No specific updates from the Release Squad.
Some useful links:
6.1 development cycle
Bug scrub cycle

Other 6.1 related items:
@pbearne: is keen to get these two filters #56045 and #37930 committed. Action: @davidbaumwald is looking into this. Anyone else able to assist too?

@jeffpaul: Worth noting that Beta 1 is in less than 3 weeks and historically we’ve tried to ensure features land week prior so ideally any new features/enhancements get in by Friday, September 9, 2022.

@webcommsat: On an admin task, the roadmap post for 6.1 does not seem to be linked from the development cycle page. Can this be added? The post also refers to a second post to follow, is this expected before Beta 1? Action: Follow-up.

@webcommsat: A question for the release leads, do we have any update on the pre-release walkthrough date? It was provisionally set for September 13, 2022.
Update Sept 1 in release leads channel: pre-release walkthrough confirmed for September 13, at 16:00 UTC. @jpantani is organizing the event via Zoom. Announcement post to follow.
Action: Add walkthrough on next week’s dev chat agenda for an update.

b) Minor releases
Key links for anyone wanting to know more about the latest minor release, 6.0.2.
WordPress 6.0.2 security and maintenance release
HelpHub page for 6.0.2

@sergeybiryukov: 6.0.2 includes 3 security fixes, 12 bug fixes for core, and 5 bug fixes for the block editor. Please update if you haven’t yet.

c) Discussion on early timeframe
Core Slack discussion highlighted by @jeffpaul: What should be the definition of the early timeframe within a major release cycle?

@clorith: Noting that the early keyword is in the workflow handbook under https://make.wordpress.org/core/handbook/contribute/trac/keywords/, and since it’s aimed specifically at committers, I would presume it’s aimed at committing early.

@davidbaumwald: @jeffpaul and I had a document somewhere that was going to be the prelude to a post about defining early.

@costdev: Just throwing this in as a consideration for the Make post: we might also consider having additional keywords for specificity. e.g. needs-early-decision, etc.

@clorith: In my head, “early discussion” is “discuss as much as you want until a decision is made, if it’s still in the discussion phase, it’s not ready for milestoning”. But that’s something that would likely come out of a make post with feedback I suspect .

@jeffpaul: I think the most important bit will be the timing of what “early” means.
Action: @clorith volunteered to draft a make/core post about it to gather input, and help cement this with a proper definition. Further discussion can be added on that post.


This has a related item on PHP.
Ticket #55603 for discussion. This issue was highlighted at a bug scrub last week. Wider feedback is requested on the approach on the ticket 2nd-opinion php82

@hellofromtonya: The above ticket is something @jrf and I will be working on following up to live working session held recently.

@hellofromtonya: Please note, WordPress Core will not be fully compatible with PHP 8.2 by the time the new PHP version is released. Handling of dynamic properties has a POC but will not be ready in time. The plan is to commit.

5. Components and tickets

Are you a component maintainer? Shepherding a ticket? Beta 1 is four weeks away, scheduled for September 20, 2022.

@sergeybiryukov:

General: Code modernization efforts have continued on preparing WordPress core for PHP 8.2. Thanks @jrf, @antonvlasenko, @costdev, and everyone testing the PHP 8.2 PRs! Ticket #56033 for more details.

@clorith

Site Health has been making strides this past week with a few tickets going in (and a few being gardened and closed as no longer relevant, or non-reproducible).

@webcommsat: Just a reminder to our other component maintainers, please do share your updates and any help you need. You can add these asynchronously to the dev chat agenda or to the Summary on the Make/ Core blog. You can also raise any tickets that you would like to highlight for help, especially if they are planned for the next release.

6. Open Floor

– Topic description core Slack channel. Action: agreed to add Dev Chat date and time.

Props to @webcommsat for the dev chat summary and @marybaum and @costdev for review, and to those who facilitated the meeting.

#6-0, #6-1, #dev-chat, #summary, #week-in-core

A Week in Core – August 29, 2022

Welcome back to a new issue of Week in Core. Let’s take a look at what changed on Trac between August 22 and August 29, 2022.

  • 33 commits
  • 99 contributors
  • 46 tickets created
  • 10 tickets reopened
  • 45 tickets closed

The Core team is currently working on the next major release, WP 6.1 🛠

The team has also started working on Twenty Twenty-Three, the next bundled theme that will be included with WP 6.1 🎨

Ticket numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Build/Test Tools

  • Automatically rerun a workflow the first time it fails – #56407
  • Enable running the tests on PHP 8.2 – #56009

Cache API

  • Remove private delegation from cache priming functions – #56386

Code Modernization

  • Explicitly declare WP-specific property in WP_SimplePie_File#56033
  • Explicitly declare all properties created in set_up() methods of various test classes – #56033
  • Explicitly declare all properties in POMO_Reader et al – #56033
  • Explicitly declare all properties in WP_Ajax_Upgrader_Skin#56033
  • Explicitly declare all properties in WP_Test_Stream#56033
  • Explicitly declare all properties in various tests – #56033
  • Remove dynamic properties in Tests_Comment_Walker#56033
  • Remove dynamic properties in WP_Test_REST_Posts_Controller#56033
  • Remove dynamic properties in WP_Test_REST_Users_Controller#56033
  • Remove dynamic properties in WP_UnitTestCase_Base#56033
  • Remove unused dynamic property in WP_Test_REST_Pages_Controller#56033

Coding Standards

  • Use strict comparisons in path_is_absolute()#36308

Docs

  • Correct typo in wp_maybe_clean_new_site_cache_on_update() parameter description – #55646

Editor

  • Block Patterns: Add new Footers category#56416
  • Backport bug fixes from Gutenberg into Core for WP 6.0.2 RC#56414
  • Ensure get_block_templates() returns unique templates or template parts – #56271
  • Ensure that timezone.offset passed to @wordpress/date is a float – #56459

Help/About

  • Improve vertical alignment in the Additional Design Tools section – #56210

Media

  • Account for Windows when normalizing file paths – #36308

Query

  • Cache post ID database query within WP_Query#22176, #55652

Site Health

  • Don’t show issue groups unless there are items in them – #47222
  • Improve the fatal error handling text in multisite scenarios – #48929
  • Introduce persistent object cache check – #56040

Themes

Props

Thanks to the 99 (!) people who contributed to WordPress Core on Trac last week: @jrf (14), @costdev (8), @SergeyBiryukov (7), @antonvlasenko (5), @desrosj (4), @johnbillion (4), @audrasjb (3), @peterwilsoncc (2), @markjaquith (2), @ironprogrammer (2), @mukesh27 (2), @DavidAnderson (2), @jorbin (2), @dd32 (2), @hellofromTonya (2), @Clorith (2), @spacedmonkey (2), @tillkruss (2), @chriscct7 (2), @knutsp (1), @mordauk (1), @talldanwp (1), @nvartolomei (1), @aspexi (1), @benoitchantre (1), @GaryJ (1), @Ipstenu (1), @TJNowell (1), @gMagicScott (1), @Otto42 (1), @mikejolley (1), @lev0 (1), @juliobox (1), @Rarst (1), @jb510 (1), @GeekStreetWP (1), @khromov (1), @ryno267 (1), @rudlinkon (1), @gregorlove (1), @marybaum (1), @JavierCasares (1), @ayeshrajans (1), @skithund (1), @zieladam (1), @tomepajk (1), @Mte90 (1), @oglekler (1), @webcommsat (1), @dougwollison (1), @weboccults (1), @sabernhardt (1), @joostdevalk (1), @swissspidy (1), @jonmackintosh (1), @uofaberdeendarren (1), @leemon (1), @georgestephanis (1), @williampatton (1), @damonganto (1), @ocean90 (1), @birgire (1), @stevenlinx (1), @Whissi (1), @kebbet (1), @sergeybiryukov (1), @scribu (1), @ryan (1), @nacin (1), @meloniq (1), @drewapicture (1), @batmoo (1), @aaroncampbell (1), @poena (1), @robinwpdeveloper (1), @palmiak (1), @rkaiser0324 (1), @davidbaumwald (1), @DrewAPicture (1), @jdgrimes (1), @furi3r (1), @crazycoders (1), @rmccue (1), @miqrogroove (1), @afragen (1), @apedog (1), @markparnell (1), @grapplerulrich (1), @earnjam (1), @mweichert (1), @joyously (1), @dingdang (1), @infolu (1), @JeroenReumkens (1), @nhuja (1), @sean212 (1), @filosofo (1), @design_dolphin (1), and @Synchro (1).

Congrats and welcome to our 4 new contributors of the week: @tillkruss, @tomepajk, @Whissi, @rkaiser0324 ♥️

Core committers: @sergeybiryukov (20), @desrosj (3), @clorith (2), @antpb (2), @peterwilsoncc (2), @noisysocks (1), @flixos90 (1), @mcsf (1), and @gziolo (1).

#6-1, #core, #week-in-core

What’s new in Gutenberg 14.0? (31 August)

“What’s new in Gutenberg…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, discovering new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project.


Gutenberg 14.0 is now available to download in the WordPress plugin repository. It’s full of enhancements, including extra blocks supports in the UI that were only available via theme.json before, a revamped List block, and much more.

Over 50 people contributed to this packed release (over 260 PRs!), 5 of them as first-time contributors.

Table of contents

Enhanced List block using inner blocks

After the Gallery block and the Quote block, it is the List block’s turn to get a new makeover and leverage inner blocks. Now your list items can be easily sorted and indented with a much-improved user experience.

Add axial gap control to Styles

Now users have the ability to adjust axial (vertical and horizontal) block spacing using the Styles UI for those blocks that support it.

Pseudo-elements supports on button elements

After first introducing the ability to control hover/active/focus states for links using theme.json, this option has been extended to button elements (this includes blocks that include such elements, like button, file, and search). Now you can style those states easily, including something like this in your theme.json file:

"styles": {
    "elements": {
        "button": {
            ":hover": {
                "color": {
                    "background": "blue",
                    "text": "hotpink"
                }
            },
            ":active": {
                "color": {
                    "background": "red",
                    "text": "yellow"
                }
            }
        }
    }
}    

Appearance tools available for opt-in via theme supports

Until now, only themes leveraging theme.json could opt-in to use Appearance tools. Now any theme can simply include in their functions.php file:

add_theme_support( 'appearance-tools' );

and it will support border styles, link color, spacing (blockGap, margin, padding), and line height.

14.0

Enhancements

  • Add optional capture group to URL regex in wp-env. (43200)
  • Core Data: Add canRead to useResourcePermissions. (43484)
  • Element: Remove enzyme from platform test. (43531)
  • [Create-block] Add --variant flag to allow creation of different block type variants. (41289)
  • Use str_starts_with. (43371)
  • [Create Block] Adding a --no-plugin flag to scaffold only block files. (41642)
  • Customize widgets: Fix top contents cutoff in keyboard shortcuts. (43391)

Design Tools

As part of the effort to improve design tool consistency for typography and spacing on blocks (43242), there’s been a lot of work done to blocks during this release to add missing supports to them.

Added typography support:

Added spacing supports:

  • Paragraph: Add spacing block supports. (43455)
  • Heading: Add padding support. (43454)
  • List: Add spacing block supports. (43402)
  • Media & Text: Add spacing block supports. (43456)
  • Post Date: Add spacing support. (43406)
  • Post Title: Add padding support. (43457)
  • Query Title: Add padding support. (43458)
  • Spacer: Add spacing block supports. (43366)
  • Table of contents: Add spacing supports. (43368)
  • Table: Add spacing block supports. (43370)
  • Tag cloud: Add spacing block supports. (43367)
  • Term description: Add spacing block supports. (43372)
  • Verse: Add margin support. (43461)
  • Video: Add spacing block supports. (43365)

Added other supports:

  • Gallery: Add background color block supports. (43294)
  • Post Featured Image: Add border support applied to inner img. (42847)
  • Social Links: Enable alpha on color pickers. (43453)
  • Social links: Add background color block supports. (43293)
  • Table of contents block: Add color block supports. (43363)

Components

  • (Custom)SelectControl: Refresh and refactor chevron. (42962)
  • Always use screen for testing-library queries. (43152)
  • Autocomplete: Use KeyboardEvent.code instead of KeyboardEvent.keyCode. (43432)
  • Card: Migrate to TypeScript. (42941)
  • ComboboxControl: Normalize hyphen-like Unicode characters to ASCII hyphens when matching search queries. (42942)
  • CustomGradientPicker: Use KeyboardEvent.code instead of KeyboardEvent.keyCode. (43437)
  • DateTimePicker: Replace react-dates and moment with useLilius and date-fns. (43005)
  • FocalPointPicker: Use KeyboardEvent.code, partially refactor tests to modern RTL and user-event. (43441)
  • FontSizePicker: Add a flag to remove bottom margin. (43062)
  • FormTokenField: Add the ability to auto-select first matching suggestion for incomplete token. (42527)
  • FormTokenField: Use KeyboardEvent.code, refactor tests to model RTL and user-event. (43442)
  • Modal: Use code instead of keyCode for keyboard events. (43429)
  • Popover: Move eslint-disable comment to the correct deps array. (43320)
  • ToggleGroupControl: Improve styling for icon options. (43060)

Block Library

  • Add a setting to hide the prefix in the archive title. (42594)
  • Embed: Update Reddit icon. (43326)
  • Post date: Add option to display as the last modified date. (42312)
  • Reset focalPoint after replacing the cover image. (42859)
  • Social Link: Update Reddit icon and color to match brand guidelines. (43325)
  • Try “constrained” content width as new layout type. (42763)
  • Try: Add a clickable Group setup state. (40664)
  • Use page list instead of placeholder as fallback. (42735)
  • [Query Loop]: Honour intended post type when previewing patterns and when replacing them with patterns. (43285)
  • List: Use nested blocks. (42711)

Global Styles

  • BlockGap: Add axial gap option to global styles where available. (42490)
  • BlockGap: Add support for spacing presets. (43296)
  • Spacing presets: Add check for 0 spacing steps. (43105)
  • Spacing presets: Add support for margins. (43246)
  • Spacing presets: Implement disabling of custom space sizes. (43216)
  • Pseudo-elements supports on button elements. (43088)

CSS & Styling

  • Placeholder: Add blurred background to work in nested cases. (43379)
  • Placeholder: Refactor and simplify dashed placeholders used for Featured Image & Site Logo. (43228)

Data Layer

  • [data] Export the type for the combineReducers export. (43516)

Site Editor

  • Template Part: Allow changing properties in focus mode. (43151)

Block Editor

  • Refactor LinkControl tests to @testing-library. (43147)

Bug Fixes

  • Create Block: Refactor handling for template variants. (43481)
  • Fix no-results grammar. (43168)
  • Fix spinner causing a flash when loading site editor. (43226)
  • Image: Fix unclickable buttons. (43361)
  • Keycodes: Fix display of symbols in keyboard shortcut modal. (43137)
  • MediaReplaceFlow: Reset default LinkControl margins. (43156)
  • Post title: Fix pasting into existing content. (43123)
  • [Block Editor]: Fix block switcher label to take into account block variations. (43309)
  • [useEntityRecord] Pass the correct kind, name, and recordId to getEditedEntityRecord. (43517)
  • wp-env: Set core source to latest when null. (43133)

Block Library

  • Ensure the block toolbar doesn’t overlap block by modifying forcePosition and shift popover props. (42887)
  • Ensure pagination numbers have an href in block edit function. (43354)
  • Fix Post Featured Image border attributes. (43426)
  • Fix classic block converted to regular blocks when clicking new ‘Edit visually’ button. (43219)
  • Fix featured image being unselectable using arrow keys. (43323)
  • Fix navigation block undefined index error on frontend. (43302)
  • Gallery block: Ensure image attributes copy correctly between transforms. (42796)
  • Home Link: Fix undo trap. (43112)
  • List v2: Copy list wrapper when copying list items. (42860)
  • Navigation: Page List fix missing padding. (43358)
  • Prevent query block from looping in classic themes. (43221)
  • Pullquote block: Avoid text-align settings affecting block width and font size. (43188)
  • Pullquote block: Remove font definition from the default block styles. (43195)
  • taxonomy-controls.js: Change REST context to “view” when fetching taxonomy terms. (43274)
  • Home Link: Properly close tags. (43706)
  • Social Link: Fix background color on WhatsApp icon. (43683)

Components

  • (Custom)SelectControl: Truncate long options. (43301)
  • AlignmentMatrixControl: Fix width bug. (43482)
  • ColorPalette, GradientPicker: Fix color picker popover positioning. (42989)
  • ColorPalette: Make sure “key” is unique when iterating over color entries with the same value. (43096)
  • Dropdown: Anchor popover to the dropdown wrapper (instead of the toggle). (43377)
  • Fix block toolbar offset in site editor when toggling sidebars. (43172)
  • Fix popover glitch that results in incorrect toolbar positioning in site editor. (43267)
  • Improve appearance of controls in the Global Styles Typography panel. (43304)
  • Popover: Fix and improve opening animation, use framer motion. (43186)
  • Popover: Make sure offset middleware always applies the latest frame offset values. (43329)
  • Refactor Guide tests to @testing-library/react. (43380)

Global Styles

  • Check for recursive dynamic reference in the site editor. (43166)
  • Duotone: Prevent early return blocking other style generation. (43300)
  • Fix dynamic references on the site editor. (42976)
  • Fix error in handling spacing preset slugs. (43237)
  • Layout: Re-instate alignwide and alignfull in flow layout get alignments. (43502)
  • Spacing presets: Fix/minor issues noted in initial UI PR. (43214)
  • Layout: Fix has-global-padding classname for constrained layouts without contentSize. (43689)

Block Editor

  • Fix Cmd+A issue in Storybook. (43145)
  • Fix drag and drop indicator before first block and after last block. (43135)
  • Fix spinner position in URLInput component. (43472)
  • Partial select: Fix selecting into image. (42983)

Design Tools

  • Border Radius: Prevent invalid css unit only styles or empty radii style attribute. (42409)
  • Border Support: Fix disabling of border style control. (43109)
  • Post Comments Count: Prevent text-decoration from affecting warning. (43497)

Site Editor

  • Do not show scrollbar when toolbar overflows the editor wrapper. (43332)
  • Fix template part focus mode resizable editor height. (43408)

npm Packages

  • Jest Preset: Ignore is-plain-obj transformation. (43179)
  • Jest Preset: Improve is-plain-obj transformation ignore. (43271)

Widgets Editor

  • Fix legacy widget form positioning in customizer. (43297)

CSS & Styling

  • Group/Stack/Row: Scope the dashed placeholder rules. (43169)

List View

  • Ensure long anchors don’t cause the List View to extend. (43134)

Post Editor

  • Post Template: Don’t fetch settings and templates for non-admin users. (42845)

Patterns

  • Fix custom placeholder not displaying on subsequent Paragraph blocks. (42519)

Accessibility

  • Block Editor: Remove aria-selected from LinkPreview. (43279)
  • Block Editor: Replace aria-owns with aria-controls in URLInput. (43278)
  • Separator: Disable the contrastChecker via block.json. (43357)
  • Fix Top toolbar buttons tooltips and style when ‘Show button text labels’ is enabled. (42815)

Performance

Lodash is known to unnecessarily inflate the bundle size of packages, and in most cases, it can be replaced with native language functionality. See these for more information and rationale: (16938, 17025, 39495)

The related PRs are: 43118, 43306, 43389, 42466, 43362, 43100, 43420, 43117, 42467, 42502, 43220, 43224, 43258, 43374, 43518, 43474, 43229, 43411, 42465, 43231, 43479, 43330, 43182, 43419

Experiments

Components

  • Font size picker: Use t-shirt sizes for the ToggleGroupControl component. (43074)

Documentation

  • Add documentation for useRootPaddingAwareAlignments in theme.json. (43463)
  • Comma is missing. (43446)
  • Convert HTML to Markdown in changelog for 13.9. (43324)
  • Handbook: Fix format API example link. (43477)
  • Stabilize the useResourcePermissions hook. (43268)
  • [Docs] Replace useState with edit in useEntityRecord usage examples. (43270)
  • Block Editor Handbook: Added missing codetabs end marker. (43185)
  • Docs: Fix some typos. (43175)

Code Quality

  • PHP: Use str_contains(). (43382)
  • PHP: Use str_starts_with. (43410)
  • Style engine: Pass options to CSS static methods. (43399)
  • Style engine tweaks. (43303)
  • Navigation block – minor refactor to classic menu conversion code. (43081)
  • Data: Bundle TypeScript types with the data package. (43315)
  • getTemplateInfo: Return stable reference to an empty object. (43155)
  • Remove duplicated ‘import’ comments. (43478)
  • Disabled: Migrate to TypeScript. (42708)

Components

  • Clean up unused and duplicate COLORS values. (43445)
  • Packages: Ensure dependencies use version ranges. (43355)
  • Swatch: Remove component in favor of ColorIndicator. (43068)
  • Update/floating UI version. (43206)

List View

  • Block list: Update block list view preferences name for consistency. (43494)

Widgets Editor

  • Use useResourcePermissions in block-library and the widgets editor. (43305)

Block Editor

  • Rich Text: Eliminate second scan when getting text content. (43207)

Global Styles

  • Theme_JSON: Use existing append_to_selector for pseudo-elements. (43167)
  • Enable appearance tools via theme_support. (43337)

Testing

  • Migrate wp editor meta box test to Playwright. (41519)
  • PHPCS: Exclude PHPUnit tests from file and class name sniffs (for Core parity). (43131)
  • PHPUnit: Let PHPUnit Polyfills match PHPUnit version. (43334)
  • PHPUnit: Turns on PHP notices and deprecations. (43102)
  • Update incorrect quote end-to-end test snapshot. (43407)
  • Update test fixture for performance test. (43359)
  • Quote: Stabilise flaky end-to-end test. (43460)

Build Tooling

  • Build Tools: Fix typo in performance tests workflow. (43153)
  • Packages: Update the minimum required Node.js version to 14 for tools. (43141)
  • ESLint Plugin: Remove all rules targeting test files from recommended presets. (43272)
  • Ignore library CSS and built CSS in stylelint. (42027)
  • Fix ‘Mark issues stale after needs testing for 30 days’ workflow. (43545)

npm Packages

  • Packages: Replace is-plain-obj with is-plain-object. (43511)

Components

  • (Custom)GradientPicker: Add flag to remove margins. (43387)
  • AlignmentMatrixControl: Improve stories. (43438)
  • AnglePickerControl: Add flag to remove bottom margin. (43160)
  • ComboboxControl: Add flag to remove bottom margin. (43165)
  • CustomSelectControl: Deprecate constrained width style. (43230)
  • DuotonePicker/DuotoneSwatch: Add stories. (43225)
  • Storybook: Add margin checker tool. (43223)
  • ToggleGroupControl: Improve stories for documentation view. (43265)
  • ToolsPanel: Tighten grid gaps. (43424)

Block Library

  • Buttons: Update selectors to work better with button elements. (43022)
  • Comments block: Remove empty block wrapper. (43383)
  • Group block: Update description to remove “layout.” (43498)
  • Image: Try different resting state for placeholder, alternate version. (43180)
  • Navigation: Try to improve the appender in an empty block. (43115)
  • Polish placeholder radius and enable duotone on image setup state. (43425)
  • Pullquote: Use inline rich text instead of multiline. (43210)
  • [Blocks] Paragraph and Heading: Add gradient support. (43119)

Patterns

  • Bundle new collection of Header and Footer block patterns. (43157)
  • Mark which attributes of the image should be considered content. (43280)
  • Prefer _x() for i18n context in core patterns. (43409)

Design Tools

  • Add margin and padding supports to Audio block. (43351)
  • Add margin/padding support to Archives block. (43350)

Global Styles

  • Add documentation about spacing presets. (43349)
  • Spacing presets: Add editor UI support. (42173)

Site Editor

  • [Site Editor]: Add success notice upon template creation. (43430)

CSS & Styling

  • Style engine: Use style engine for block supports CSS in editor. (43055)
  • Style engine: Remove enqueue flag. (43103)

Block Editor

  • Merging blocks: Allow x to be merged into wrapper blocks (quote, list, group…). (42780)

Tools

Testing

  • Refactor Button tests to @testing-library/react. (42981)
  • Refactor Guide PageControl tests to @testing-library/react. (43148)
  • Refactor MenuGroup tests to @testing-library/react. (43275)
  • Refactor withSpokenMessages tests to @testing-library. (43273)
  • Editor: Refactor PostAuthorCheck tests to @testing-library. (43176)
  • Editor: Refactor ThemeSupportCheck tests to @testing-library/react. (43532)
  • Editor: Refactor a few component tests to @testing-library/react. (43376)
  • Components: Refactor Placeholder tests to @testing-library/react. (43069)
  • Components: Refactor Tooltip tests to @testing-library/react. (43061)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

Post Editor

VersionTime to the first blockKeyPress Event (typing)
Gutenberg 14.09.99 s43.36 ms
Gutenberg 13.93.95 s54.77 ms
WordPress 6.04.31 s59.53 ms

Site Editor

VersionTime to the first blockKeyPress Event (typing)
Gutenberg 14.011.45 s34.75 ms
Gutenberg 13.95.17 s29.37 ms
WordPress 6.04.92 s20.11 ms

Contributor Props

The following contributors merged PRs in this release:

@aaronrobertshaw @adamziel @afercia @andrewserong @aristath @awps @carolinan @ciampo @derekblank @dinhtungdu @dmsnell @draganescu @drzraf @ellatrix @geriux @glendaviesnz @gziolo @hellofromtonya @hz-tyfoon @jasmussen @jostnes @kdevnel @MaggieCabrera @Mamaduka @markbiek @matiasbenedetto @mcsf @mirka @ndiego @noahtallen @noisysocks @ntsekouras @oandregal @ockham @paulopmt1 @pbking @ramonjd @randhirexpresstech @Rink9 @ryanwelcher @scruffian @SiobhyB @Soean @t-hamano @talldan @tellthemachines @titusdmoore @torounit @tyxla @walbo

The following PRs were merged by first-time contributors:

  • @drzraf: taxonomy-controls.js: Change REST context to “view” when fetching taxonomy terms. (43274)
  • @markbiek: ComboboxControl: Normalize hyphen-like Unicode characters to ASCII hyphens when matching search queries. (42942)
  • @randhirexpresstech: Add font family and text-decoration typography supports to paragraph blocks. (39642)
  • @Rink9: Migrate wp editor meta box test to Playwright. (41519)
  • @titusdmoore: Add optional capture group to URL regex in wp-env. (43200)

Kudos to all the contributors that helped with the release! 👏

Props to @gziolo @priethor @joen @bernhard-reiter @scruffian @oandregal for their assistance with the release.

#gutenberg, #gutenberg-new

Editor chat summary: 31 August, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, August 3, 2022 at 02:00 PM UTC. in Slack. Moderated by @andraganescu.

Gutenberg plugin releases

Key project updates

Key project updates:

Task Coordination

@mamaduka

@onemaggie

@andraganescu

Open Floor

Announcements, questions and discussions.

@luminuu

Are there plans to prioritize [the blocking] changes [for new TwentyTwentyThree style variations] until the Feature Freeze (which should be Beta 1)?

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Agenda, Dev Chat, August 31, 2022

The weekly WordPress Developers Chat on Wednesdays August 30, 2022 at 20:00 UTC.
All are welcome to join the chat in the #Core channel of the Make WordPress Slack.

1. Welcome

Last week’s meeting summary – thanks to @webcommsat for writing. A volunteer is needed to draft the meeting summary from August 31 – could this be you?

2. Announcements

WordPress 6.0.2 security and maintenance release went live on August 30, 2022. Thanks to everyone who was involved. Please download and test.

3. Blog posts

Core editor improvement: refining the template creation experience (August 25, 2022)

A Week in Core (will be added to this post once it is published)

Got a post on WordPress.org to share for dev chat? Add it to the comments.

4. Upcoming releases

a) The next major is 6.1.

Update from the release squad and any questions.
6.1 development cycle
Bug scrub cycle

b) The next minor

Update from those leading the minors for 6.0.
WordPress 6.0.2 security and maintenance release
HelpHub page for 6.0.2

c) Discussion on early timeframe

What should be the definition of early timeframe within a major release cycle? (read the discussion on the core Slack) – thanks to @jeffpaul for highlighting

5. Components and tickets

Are you a component maintainer? Shepherding a ticketBeta 1 is four weeks away, scheduled for September 20, 2022.

Ticket #55603 for discussion. This issue was highlighted at the bug scrub last week hosted by @audrasjb. Wider feedback is requested on the approach on the ticket towards increased PHP 8.2 compatibility. 

6. Open floor

Please add your item to the comments.

#agenda, #dev-chat

Summary, Dev Chat, August 24, 2022

These are the notes from the weekly WordPress developers chat held on Wednesday August 24, 2022.

1. Welcome and introduction

2. Announcements

WordPress 6.0.2 RC 1 has landed! Please download and test.

3. Blog posts

This is not all the posts published on the core blog during the last week, but major items highlighted for comment or queries.

A week in core (published August 25, 2022) – thank you @audrasjb

Feedback by September 9, 2022 is requested on a new system for updating HTML attributes.

The 16th Full Site Editing Call for Testing is still open. This features a simpler testing exercise. Deadline is September 2, 2022. Thanks @annezazu for the update.

4. Upcoming releases

a) The next major is 6.1.

@marybaum shared that @priethor has asked for green-yellow-red lights looking ahead to beta release and almost all green were reported in the #6-1-release-leads channel.
No other updates were received on the agenda or during the meeting from the squad.

b) The next minor is 6.0.2.
The Release Candidate (RC1) is out.

Update via @sergeybiryukov

5. Components and tickets

This section is for updates from component maintainer or anyone shepherding a ticket. Beta 1 is five weeks away, so the time is ripe!

Updates from @sergeybiryukov for Build/Test Tools, Database, General, Themes, Date/ Time components

Build/Test Tools

As of yesterday, PHPUnit test runs on GitHub Actions include PHP 8.2, though addressing compatibility issues is still a work in progress. PHP 8.2 is expected to be released at the end of November 2022. Thanks @jrf.

More details at: Ticket #56009 Prepare for PHP 8.2

Compatibility with the recent versions of MariaDB (10.6+) and MySQL (8.0+) was improved. With these and some other changes, specifically skipping tests for non-implemented REST API methods, most of the test runs from various hosting environments on the Host Test Results page successfully pass now, except for PHP 8.2.0alpha2 for now.

More details at: Tickets #51740 and #53623

Database

General: Code modernization efforts have continued on preparing WordPress core for PHP 8.2.

Thanks @jrf and @antonvlasenko.

More details at: Ticket #56033 PHP 8.2 explicitly declare all known properties

Themes

  • A Block Themes filter is now available on the Add Themes screen, to match a similar filter in the WordPress.org Theme Directory. Thanks @luminuu and @audrasjb.
    Ticket #56283 Add “Block theme” filter under “Add themes” for more details.
  • The support for Update URI theme header was added to core. This allows third-party themes to avoid accidentally being overwritten with an update of a theme of a similar name from the WordPress.org Theme Directory. Thanks @dd32@meloniq, @costdev
  • Changeset [53933] and ticket #14179 for more details.

Thanks everyone who contributed to those tickets! 

Date/Time, I18N components

Permalinks: No major news this week.

Site Health component

@clorith:

  • Tickets #54508 (add more information to site health message) & #54617 (add more details when site health checks fail) could benefit from copy review; @webcommsat and @marybaum will follow up.

Updates on Help/About and Bulk/ Quick Edit components

@marybaum: We moved one ticket on: #56210.

Thanks @webcommsat @ogleckler @nalininonstopnews and @sergeybiryukov for comments / discussion on components in these two components. Thanks for the commit @audrasjb.

@nalininonstopnewsuk:

Quick Edit/ Bulk edit – on the next few Mondays we will continue to look at some of the tickets and doing some triage. We did some exploration on one particular ticket this last week. We will bring it to a bigger scrub potentially after that depending on progress.

As Mary had lost her internet connection, @nalininonstopnewsuk added: Thank you everyone for sharing. Dev chat is a good place for component maintainers to be able to share progress on their tickets and highlight any issues. You can let the core team reps know if you need some assistance too. 

As a newer maintainer, I appreciate the outreach from the team reps and from documentation at releases time. Dev chat also helps get more people to look at a specific point in an issue if needed. Just putting in my thoughts. @marybaum: Very valuable! Thanks so much.

Upgrade/ Install component

@costdev: Upgrade/Install: While we’ve had reviews from individual committers who happen to be on the Security, Docs and Polyglots teams, we’d like to make an official request to these teams here in dev chat and in their respective channels to review the Rollback Update Failure feature plugin for any potential issues.

No further update from maintainers nor tickets. Thanks everyone who has added tickets above.

6. Open Floor

@marybaum: We are going to talk about dev chat at WordCamp US Contributor Day.

There were no other items added to the agenda today apart from the links we have already shared. Nothing else was raised.

@marybaum: Also huge thanks, Nalini, for stepping in and helping lead this chat today! Thanks and for the info you have sent across on some words for the glossary relating to the handbook Nalini. @nalininonstopnewsuk: Thank you for the handbook link about what dev chat does and its purpose. It is very interesting and useful.

Props to: @webcommsat for the dev chat summary, and @marybaum, @nalininonstopnewsuk, and @costdev for review.

#6-0, #6-1, #dev-chat, #summary