The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.?Create a ticket in our bug tracker.
Thanks to the 42 contributors of the past week, including 7 new contributors! Kudos to the 4 coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too.
Next minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.(s)
They will publish a schedule for 5.8.2 and –if needed– 5.8.3 on September 23.
Next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.
Concerning the next major release —WordPress 5.9— a planning roundup was published a couple weeks ago.
@audrasjb proposed to start to schedule bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs for the milestone. He will run the first scrub of 5.9 on Thursday September 23, 2019 at 20:00 UTC.
Reminder: everyone is welcome to run a bug scrub on the #coreSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. If you are interested, please read this handbook post: Leading bug scrubs. And yes, that’s a call for volunteers 🙂 Please add a comment below if you want to help.
For 5.9, @hellofromtonya pointed out that it would be nice to try to also plan some APAC-friendly bug scrubs when possible.
Some changes were implemented to make the PHPUnit Polyfills loading more flexible and improve the related messaging. See changesets 51810-51813 and ticketticketCreated for both bug reports and feature development on the bug tracker.#46149 for more details.
The PHPUnit Polyfills package and related test infrastructure changes are now backported to a few older branches (WP 5.8 to 5.2). This makes it easier for developers to continue testing on multiple versions of WordPress while adding tests for newer versions of PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher, which require more modern PHPUnit practices. See changesets 51838-51840, 51843-51846 and ticket #53911 for more details.
Work is now complete on Modernizing to the Latest PHPUnit version. Dev notedev noteEach important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:
a description of the change;
the decision that led to this change
a description of how developers are supposed to work with that change.
Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. is being reviewed and plan is to publish on Monday.
PHP 8.1: work is nearly complete, i.e. identified through tests. Will be shifting shortly into community feedback and open call for contributions to identify and help fix compatibility issues.
A translator comment was added to clarify the “BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.” string in the Block widgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. settings form. This should reduce confusion for Polyglots translating the string.
While the Block Widgets Editor was released with WordPress 5.8, the work to improve the experience hasn’t stopped to help even more folks use blocks to build out widgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. areas in an endless number of ways. The latest in a series of improvements comes with the launch of Gutenberg 11.5 that introduces a Widget Group block. This new blockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. replicates the familiar experience of being able to add a title to a group of blocks and allows you to group any block, making it easier to move and layout content however you’d like. This both helps with compatibility for older themes when migrating over to the new editor and enables a more cohesive experience for building out widget areas.
For example, before this update, it was tricky to get the spacing right for adding a headerHeaderThe header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. above another set of blocks. Now, you can do that with ease:
Video showing how to use the Widget Group Block.
This also makes it a breeze to move collections of blocks into new widget areas:
Video showing how you can drag and drop a collection of blocks within the Widget Group Block.
As always, you can also make these changes in the CustomizerCustomizerTool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.! For more general information about the Block Widgets Editor, check out the Dev note and the user documentation. To get involved in this work, head to #feature-widgets-block-editor and explore the GitHub tracking project to see what’s next.
Next minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: WP 5.8.2
Next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: WP 5.9
Components check-in and status updates
Check-in with each component for status updates.
Poll for components that need assistance.
Open Floor
Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?
Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.
This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.
Welcome back to a new issue of Week in CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between September 13 and September 20, 2021.
21 commits
42 contributors
31 tickets created
0 tickets reopened
23 tickets closed
The Core team is currently working on the next point (5.8.2) and major (5.9) releases 🛠
TicketticketCreated for both bug reports and feature development on the bug tracker. 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
BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor
Expect an absolute path in WP_TESTS_PHPUNIT_POLYFILLS_PATH constant – #46149
Improve messaging when PHPUnit Polyfills cannot be found – #46149
Improve messaging when PHPUnit Polyfills do not comply with version requirements – #46149
Make WP_TESTS_PHPUNIT_POLYFILLS_PATH more flexible – #46149
Reworks Tests_Option_Option::test_bad_option_names() into data provider – #53635
Bundled Themes
Twenty Eleven: Set a fixed height for search form when headerHeaderThe header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. image is added – #40398
Twenty Seventeen: Make blogblog(versus network, site) header margin more specific on front page – #43628
Twenty Twenty-One: Add missing escaping for the “Secondary menu” label – #54127
Coding Standards
Code Modernization: Fix “passing null to non-nullable” deprecation notice in WP_Comment_Query::get_comment_ids() – #53635
Rename the $arrURL variable to $parsed_url in WP_Http::request() – #53359
Rename the $arrURL variable to $parsed_url in WP_Http_Cookie::__construct() – #53359
Rename the $arrURL variable to $parsed_url in WP_Http_Streams::request() – #53359
Rename the $processedHeaders variable to $processed_headers in WP_Http::request() – #53359
Use strict comparison in wp-inclues/class-wp-http-cookie.php – #53359
Documentation
Update description for the $wp_version global – #53413
Embeds
Add Pinterest as a trusted oEmbed provider – #53448
Internationalization
Add a translator comment to clarify the “Block HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.” string in the Block widgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. settings form – #54110
Media
Fix $content parameter default value in img_caption_shortcode() – #53635
Options, MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. APIs
Fix “passing null to non-nullable” deprecations to (get|add|update|delete)_option() – #53635
Upgrade/Install
Create a temporary backup of plugins and themes before updating – #51857
All coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS files have now been claimed, and are either in progress or have a PR, however @dryanpress reminded us that if anyone has claimed a file and can no longer work on it please do let us know
The next step is reviewing and merging PRs. Help is very welcome if anybody is up for “trying out a PR and making sure the colors still look correct (or correct enough, where maybe we made changes)“
@dryanpress raised the topic of skinning adminadmin(and super admin) colour schemes, as there are some custom properties for body.admin-color-ectoplasm already in custom-properties.css. We would probably create a couple of colour schemes at a later stage, for testing & demonstration purposes
@dryanpress outlined the final todo list for the project:
Merge all remaining files
Look for duplication and opportunities for property consolidation
Final team review
Merge proposal write-ups
@ryelle added that, before the final team review step, discussion will be needed about what to consolidate and how, for example rgba and box-shadow values
@ryelle added that, as there are several PRs now merged, anybody interested could start generating some ideas for these next steps right now
@dryanpress asked if we are still on target for an --experimental release in 5.9 which @ryelle confirmed we have good momentum for
@ryelle observed that there are other places outside of CSS files where CSS is used, for example php and js files, which also need to be reviewed. @dryanpress offered to add this and the other tasks (mentioned above) to the planning document
@danfarrow had quickly calculated there are now 127 custom properties in custom-properties.css. @robertg added that this isn’t including the 225 (approx) in his PR
This post was authored by @opr18 (Thomas Roberts).
During a recent WordPress #core-js meeting there was a discussion about updating the JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. coding standard. The specific update that is being proposed is to change the rules relating to comments.
Currently, the standard reads:
Comments come before the code to which they refer, and should always be preceded by a blank line. Capitalize the first letter of the comment, and include a period at the end when writing full sentences. There must be a single space between the comment token (//) and the comment text.
The proposal is that the new wording should be:
Comments come before the code to which they refer, and should always be preceded by a blank line. Unless writing a linter override, or a `@see` type comment, capitalize the first letter of the comment, and include a period at the end. There must be a single space between the comment token (//) and the comment text.
The problem with the current guideline is that it is not enforceable by automated tools. It is hard for linting tools to easily distinguish between what is and isn’t a full sentence in the context of code comments.
Code reviews can quickly fill up with noisy comments and suggestions to capitalise or add periods to code comments. If this were fixable with a linting rule then these comments wouldn’t be necessary.
There are instances where it may not make sense to write in sentence case, for example: adding linter overrides or writing `see` comments where the comment may just be the name of a method or file, etc. so we would not enforce the rule on these types of comments.
If this guideline were to be amended, there would be several instances of code in the GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repository alone that do not follow it. It would be necessary to create a PR that fixes all of these issues. Because the change only relates to comments, a single PR can be made addressing all instances of comments that don’t follow the guideline, because the rule relates to comments only, this would have no impact on functionality so minimal testing would be required.
WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. currently uses JSHint for linting JavaScript files, and it does not appear that even the existing style guideline is enforced. Even so, if efforts were made to move to ESLint in WordPress core, implementing a fix for any comments that do not follow the standard should be straightforward.
Initially the rule could be enforced as a “warning” while the PR to fix the issues is completed and after it has been merged the rule could graduate to an “error”.
Here is a draft PR demonstrating the punctuation aspect of the proposed change: https://github.com/WordPress/gutenberg/pull/34964
As a part of next steps, this post is looking for feedback on:
How do you feel about the proposed changes to the wording of the standard?
Are there any concerns about the plan for implementing this change?
This proposal is open for feedback until October 5th, 2021 at which point a final decision will be made during #core-js office hours that day.
GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 11.6 RC will be released Wednesday.
Navigation BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. & Navigation Editor.
Template editor.
Patterns.
Styling.
Mobile Team.
Task Coordination.
Open Floor.
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.
The aim of the meeting is to discuss the four years old ticketticketCreated for both bug reports and feature development on the bug tracker.#22316 and two PRs that have been proposed to solve it.
Let’s try something different! A Zoom call 🙂 I will drop the link to it in the Slack channel at the start of the meeting.
Got something to propose for the agenda? Please leave a comment below.
Preliminary Roadmap, a quick overview of the main areas and features currently underway for 5.9 in GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/.
Gutenberg 11.5.0
Gutenberg 11.5.0 was released on 16th September, this update includes BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Gap support, improved support for Flex Layouts, performance improvements, and additional design tools. Check out the release post for a complete list of features and enhancements:
Monthly Plan
The monthly update containing the high-level items that Gutenberg contributors are focusing on for June are:
Template Editor
Patterns
Global Styles and theme.jsonJSONJSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.UIUIUser interface
Work is still progressing on migrating the navigation editor fully over to the REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.. The REST API changes have been merged, and now the front end code is being updated.
Lots of UI changes this week with the editor top bar being updated, the main block inserter added, and fixes to the block’s styles.
Also in general, we’re always looking for contributors to help work on the Nav Editor and bloc, if you’re interested please head over to the #feature-navigation-block-editor Slack channel. Look forward to seeing you there.
As a nice side-effect, we might get a simple APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. for saving changes in any editor that acts on entities through blocks (e.g. the widgets editor).
Inline preview support for Instagram, Vimeo. Now supporting all 5 most-used providers (YouTube, Twitter, WordPress, Instagram, Vimeo).
Fixes
Refresh embed preview when switching light/dark mode
Use device’s localeLocaleA locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English. in embed previews
Ensure inserter button is in view when RTL
Translate column block’s control labels
In Progress
Embed block.
GSS Font size, line height, colors.
Task Coordination
Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.
Simple PR’s to get the ball rolling as long as one is approved I guess we can merge multiple similar ones.
Worked on implement the new custom gradient picker design.
Currently working on the new color palette editor.
For the next week I will continue with improving the global styles related components.
Will see how can I best help the effort of implementing the new sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. with its navigation system.
Will try to dedicate attention to old PR’s I have that are mostly ready.
Mosaic view and block awareness of global styles I hope to merge them so my head becomes free for other challenges and we can submit follow ups on them.
Some further planning for the Typography Panel features in Global Styles, which will use the same ToolsPanel component recently introduced alongside the new Dimensions Panel.
Mainly have been doing some light triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., amplifying the current block theme switching exploration.
Working on updating the Gutenberg pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party description (PR coming).
Hoping to ship an additional coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. editor improvement post too in the next week.
Adding Global Inserter to Navigation Editor screen.
Experimenting with Theme JSON as means to control many aspect of Navigation block.
Fixes from the High priority section of Nav Editor tracking issue.
Various Link UI issues.
Added “help” descriptions for the various HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. element options on the Group block.
Working on how to make the Nav Editor more resilient to changes in the Navigation block. Currently it’s very difficult and not at all resilient.
One route I’m exploring is using Theme JSON to control the features of the Nav block. My proposal does two things that I’d like some input on:1. opens up `theme.json` for extensibility by developers via hooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same./filters.
Allows `theme.json` to control features that are unique to particular blocks (as opposed to things that are common across all blocks such as spacing).
I’d really like to understand whether this is within the intended scope for Theme JSON.
This has large utility outside Nav Editor because I imagine Themers wanting to be able to control multiple facets of blocks (and not just common things such as padding/margin…etc) without having to use complex hooks/filters
It’s been two weeks since 11.4, so it’s time for another GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ release, 11.5!
This update includes BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Gap support, improved support for Flex Layouts, performance improvements, and additional design tools.
Theme / Block Gap Support
Block Gap support adds the ability for blocks to opt-in to a control that allows users to choose the distance between items within a block.
With Block Gap support in place, it has also been added to the Columns, Title, and Navigation blocks.
Buttons in the the Buttons Block move closer together or farther apart as the Block Gap is changed.
Flex Layout Highlights
Following the introduction of Flex Layout in 11.2.0, now Flex Layouts are supported within the Social Links and Group blocks! The Social Links block now has a ‘flex’ justification option, for automatic best-fit.
There is also a new variation of the Group block that allows for flex layout. You can try it out by choosing “Row” from the block inserter.
Social Icons change flow when flex justification is selected.
Site Title and Logo Inside Navigation Block
It’s now possible to build your site logo or title directly into menus, enabling new design possibilities! Insert, and modify the title or logo that you prefer, using design tools, then re-order for your ideal look.
A Site Logo is added to a Navigation Block, then resized and placed.
Global Styles
Global styles are now available to themes by default, allowing block, theme, and patterns to have a reliable set of styles provided by coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
Themes are now able to selectively disable text and background colors. This allows theme authors to provide exactly the experience they’d like to provide users, whether allowing custom colors, gradients, or only their curated selections.
Other Notable Highlights
The Heading Levels menu has been redesigned, and is now vertical, making it easier to visualize the hierarchy.
New vertical Heading Levels menu, with H2 selected.
11.5.0
Features
Design Tools
Block Support: Add gap block support feature. (33991)
Enhancements
AccessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)
Media Placeholder: Change media URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org input type to allow a local URL path. (29138)
Block Library
Columns Block: Use blockGap between Columns blocks. (34456)
Query Pagination Next/Previous: Add an arrow attribute and sync next/previous block’s arrow. (33656)
Site Logo Block: Update block description to be concise. (34471)
Site Title Block: Update block description to be concise. (34475)
Social Links Block: Use the new flex layout. (34493)
Video Block: Use existing video poster image on insert. (34415)
Components
MenuItem: Add right padding for unchecked radio and checkbox items. (34406)
ToggleGroupControl: Update stories to use knobs. (34497)
Core Data
Add isRawAttribute to entity configuration. (34388)
Design Tools
Add wide alignment control only if theme provides layout.wideSize. (34586)
Update justification control in flex layout. (34651)
ToolsPanel: Change icon from horizontal to vertical ellipsis. (34369)
Full Site Editing
Limit FSE adminadmin(and super admin) notices to the Themes screen. (34353)
Global Styles
Allow disabling text and background color via theme.json. (34420)
Make global styles available to all themes. (34334)
i18ni18nInternationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.
Add context to ‘none’ strings for better translations. (34341)
Make permalinks documentation URL translatable. (34282)
Add default editor styles applied to themes without theme.json and without editor styles. (34439)
Widgets Editor
Add ‘WidgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Group’ block to widgets screens. (34484)
Allow themes with theme.json to opt-out of block gap styles. (34491)
Bug Fixes
Accessibility
Fix button block focus trap after a URL has been added. (34314)
Block Editor
Fix menu item padding regressionregressionA software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.. (34435)
Heading Block, Paragraph Block: Fix long strings of text without spaces overflow the block. (34222)
Gallery Block: Fix bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. with stalled upload when image size too large. (34371)
Gallery Block: Fix media placeholder height in site editor. (34629)
Gallery Block: Fix problem with overflowing captions on new gallery block format. (34402)
Latest Posts: Fix various ReactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. warnings in development log. (34428)
Border Controls: Display color indicator and check selected color. (34467)
Border Support: Fix check for displaying border support panel. (34516)
Gap block support: Force gap change to cause the block to re-render (fix Safari issue). (34567)
Letter Spacing: Group letter spacing correctly under typography supports. (34515)
Global Styles
Fix block-level global styles color panels. (34293)
Font Appearance Control: Fix error in global styles for Site Title in TT1-Blocks. (34520)
MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Boxes
Change default value of enableCustomFields to undefined. (33931)
Fix metaboxMetaboxA post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. reordering. (30617)
Packages
Blocks: Register block when invalidinvalidA resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. value provided for the icon. (34350)
Core Data: Add ‘include’ to the query key. (34583)
Core Data: Use resolveSelect instead of select in saveEntityRecord. (34584)
Interface: Block Toolbar & Popover component – Prevent sticky position from causing permanently obscured areas of the selected block. (33981)
Scripts: Only use svgr/webpack in js files. (34394)
Scripts: Convert legacy entry point arguments for compatibility with webpack 5. (34264)
REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.
Default batch processor: Respect the batch endpoint’s maxItems. (34280)
Widgets Editor
Fix Block Settings sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. unexpectedly collapsing. (34543)
Legacy widget’s preview functionality is broken when the page is moved. (34384)
Prevent focus trap in Legacy Widget block’s preview iframeiframeiFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.. (33614)
Performance
Block Editor
Improve the getBlock and getBlocks performance. (34241)
Rich Text: Replace global event handlers with local ones. (34492)
Rich text (core): OnFocus method can be replaced with HTMLElement.focus. (32054)
Use Setting: Consolidate the PATHS_WITH_MERGE constant to one instance. (34407)
Block Library
Gallery Block: Add docblockdocblock(phpdoc, xref, inline docs) comments to the new gallery hooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.. (34562)
Gallery Block: Remove IE specific CSSCSSCascading Style Sheets. hacks. (34372)
Button Block: Replace global shortcut event handlers with local ones. (34498)
Navigation Block: Refactor to use generic classnames. (34171)
Navigation Link Block: Replace global shortcut event handlers with local ones. (34500)
Fix linting error in trunktrunkA directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. (34464)
Linting: Remove global event listener warning. (34528)
More work on the stability of the performance metrics. (34229)
PluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party
Added janw-me to the Codeowners for the PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher FSE folder. (32990)
Jest Preset: Restore the default setting for the verbose option. (34327)
Make Test_Widget compatible with WP_Widget. (34355)
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.
Version
Loading Time
KeyPress Event (typing)
Gutenberg 11.5
6.71s
40.42ms
Gutenberg 11.4
6.80s
44.79ms
WordPress 5.8
7.53s
50.72ms
Kudos to all the contributors that helped with the release! 👏
Thanks to @beafialho and @joen for the release post assets, @priethor for coordination and review, @youknowriad for release and tools wrangling, @mamaduka for answers and help throughout, and @talldanwp for inviting me to shadow a release in preparation.
You must be logged in to post a comment.