Title: 2021 – Page 42 – Make WordPress Core --- # Yearly Archives: 2021 [ ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/) 1:49 pm _on_ April 15, 2021 Tags: [agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/), [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/)    # 󠀁[CSS Chat Agenda: April 15, 2021](https://make.wordpress.org/core/2021/04/15/css-chat-agenda-april-15-2021/)󠁿 This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for [Thursday, April 15, at 5:00 PM EDT](https://www.timeanddate.com/worldclock/fixedtime.html?msg=WordPress+CSS+Core+Chat&iso=20210415T17&p1=418&ah=1). This meeting will be held in the [#core-css](https://make.wordpress.org/core/tag/core-css/) channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). If there’s any topic you’d like to discuss, or if you have suggestions for discussion questions, please leave a comment below! * Housekeeping * Review discussion outcomes from last week (CSS deprecation path, JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. targeting naming conventions) * Project Updates - CSS Audit ([#49582](https://core.trac.wordpress.org/ticket/49582)) - Color Scheming ([#49999](https://core.trac.wordpress.org/ticket/49999)) * Open Floor + CSS Link Share [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core-css](https://make.wordpress.org/core/tag/core-css/) [ ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/) 9:46 pm _on_ April 14, 2021 Tags: [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [editor ( 223 )](https://make.wordpress.org/core/tag/editor/), [gutenberg ( 547 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-new ( 217 )](https://make.wordpress.org/core/tag/gutenberg-new/)    # 󠀁[What’s new in Gutenberg 10.4? (14 April)](https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/)󠁿 Two weeks have passed since the last GutenbergGutenberg The 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/](https://wordpress.org/gutenberg/) release, which means a new version is already available! Gutenberg 10.4 introduces cool features like blockBlock Block 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. widgets in the CustomizerCustomizer Tool 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., enhancements to the Site Editor, improvements to rich text placeholders, and, as always, many bugbug A 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. fixes as well. ## Block widgets in the Customizer As part of the Block-based WidgetWidget A 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. Editor project, one goal is to [enable block widgets in the Customizer](https://github.com/WordPress/gutenberg/pull/29549), with Gutenberg 10.4 introducing the first iteration of this feature. ## List View design updates This release brings us a set of design updates to the Site Editor List View, including [updates to icon sizes and spaces](https://github.com/WordPress/gutenberg/pull/30455) and [new colors for hover, focus, and select states](https://github.com/WordPress/gutenberg/pull/30303). ## More descriptive publishing UIUI User interface The publishing content UI found in block editors [now includes the site icon and name](https://github.com/WordPress/gutenberg/pull/30231) so that it’s clearer in certain cases, such as full-screen or mobile, where you are publishing to. [[ ## Revert template to theme defaults within the Site Editor Until now, to revert a template to the default provided by a theme, it had to be done outside the Site Editor. Thanks to this new feature, it is now possible to [revert template customizations directly in the editor](https://github.com/WordPress/gutenberg/pull/28141). [[ ## Rich text placeholder enhancements To improve the editing experience, rich text block placeholders have seen a few tweaks in this release. Starting in Gutenberg 10.4, blocks containing rich text will display a [shorter placeholder text](https://github.com/WordPress/gutenberg/pull/29611) that [will remain shown](https://github.com/WordPress/gutenberg/pull/30393) even when being focused. ## Improvements to Navigation Block The Navigation Block has good momentum and has received many improvements in this release, including a [new “Post Format Link” variation](https://github.com/WordPress/gutenberg/pull/30403), a [clearer placeholder state](https://github.com/WordPress/gutenberg/pull/30281), and more style polishing.  ## Editor and frontend parity refinement Providing a [consistent markup between the editor and the frontend](https://github.com/WordPress/gutenberg/issues/29976) is key to deliver a smooth editing experience. Gutenberg 10.4 iterates towards this goal by ensuring a frontend-editor parity in blocks such as [Quote](https://github.com/WordPress/gutenberg/pull/30190), [Separator](https://github.com/WordPress/gutenberg/pull/30255), and [Archives](https://github.com/WordPress/gutenberg/pull/30141), among others. ## **10.4** ### Enhancements * Ensure Frontend/Editor block styles parity: - Archives. ([30141](https://github.com/WordPress/gutenberg/pull/30141)) - Latest Comments. ([30134](https://github.com/WordPress/gutenberg/pull/30134)) - Quote. ([30190](https://github.com/WordPress/gutenberg/pull/30190)) - Separator. ([30255](https://github.com/WordPress/gutenberg/pull/30255)) ([30235](https://github.com/WordPress/gutenberg/pull/30235)) - Make the default padding match the browser’s default padding. ([30277](https://github.com/WordPress/gutenberg/pull/30277))( [30520](https://github.com/WordPress/gutenberg/pull/30520)) * Block Library: - Latest Comments: Remove list padding and margin. ([29402](https://github.com/WordPress/gutenberg/pull/29402)) - Post Date: Add option to make it a link. ([30499](https://github.com/WordPress/gutenberg/pull/30499)) - Post ExcerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox.: Fix toolbar for post excerpt warning. ([30280](https://github.com/WordPress/gutenberg/pull/30280)) - Post Title: Fix “‘length’ of undefined” error. ([30208](https://github.com/WordPress/gutenberg/pull/30208)) - Preformatted: Add color controls. ([28396](https://github.com/WordPress/gutenberg/pull/28396)) - Query: Use a WordPress loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. [https://codex.wordpress.org/The_Loop](https://codex.wordpress.org/The_Loop) for the query block. ([30405](https://github.com/WordPress/gutenberg/pull/30405)) - Search: Add border radius support. ([30227](https://github.com/WordPress/gutenberg/pull/30227)) - Site Logo: Style polishing. ([30526](https://github.com/WordPress/gutenberg/pull/30526)) - Template Part: Add padding support to template parts. ([29779](https://github.com/WordPress/gutenberg/pull/29779)) - Update placeholder text across blocks. ([30404](https://github.com/WordPress/gutenberg/pull/30404)) * RichText: - Add min width to show caret for empty inline container. ([30224](https://github.com/WordPress/gutenberg/pull/30224)) - Always show placholder on focus. ([30393](https://github.com/WordPress/gutenberg/pull/30393)) * General Interaface: - Add site icon and name to the publish flow. ([30231](https://github.com/WordPress/gutenberg/pull/30231)) - Use a darker canvas color. ([30282](https://github.com/WordPress/gutenberg/pull/30282)) - Update the save button label in the site editor. ([30439](https://github.com/WordPress/gutenberg/pull/30439)) * Icons: - Polish media & text icons. ([30239](https://github.com/WordPress/gutenberg/pull/30239)) - Update “close small” icon so that its shape matches the “add” icon dimensionally.( [30014](https://github.com/WordPress/gutenberg/pull/30014)) - Update site-logo block icon. ([30211](https://github.com/WordPress/gutenberg/pull/30211)) * Inserter: Clarify that when the Inserter is open clicking the + button in the top bar will close it again. ([29759](https://github.com/WordPress/gutenberg/pull/29759)) * Writing Flow: Use a shorter writing prompt. ([29611](https://github.com/WordPress/gutenberg/pull/29611)) * List View: Improve the spacing, colors and icons ([30455](https://github.com/WordPress/gutenberg/pull/30455))( [30303](https://github.com/WordPress/gutenberg/pull/30303)) * Block Themes: Clarify the empty block templates message. ([30145](https://github.com/WordPress/gutenberg/pull/30145)) * Site Editor: - Allow reverting custom templates to their original theme-provided files. ( [28141](https://github.com/WordPress/gutenberg/pull/28141)) - Use “Custom Styles” label to signal there are global styles changes in the saving panel. ([30521](https://github.com/WordPress/gutenberg/pull/30521)) ### Bug Fixes * Inserter: Show only the patterns that use allowed blocks. ([30300](https://github.com/WordPress/gutenberg/pull/30300)) * Block Library: - Buttons: Prevent overlapping button blocks in the frontend. ([30253](https://github.com/WordPress/gutenberg/pull/30253)) - Columns: Prevent having a width > 100%. ([30229](https://github.com/WordPress/gutenberg/pull/30229)) - Cover: Add ‘object-position’ to allowed inline style attributes list. ([30243](https://github.com/WordPress/gutenberg/pull/30243)) - Gallery: Avoid adding all media items in galleries using external URLs. ([30122](https://github.com/WordPress/gutenberg/pull/30122)) - Image: Do not preserve custom sizes when replacing images. ([29919](https://github.com/WordPress/gutenberg/pull/29919)) - Query: * Fix undo trap during creation. ([30203](https://github.com/WordPress/gutenberg/pull/30203)) * Pagination Numbers: Print nothing if content is empty. ([30554](https://github.com/WordPress/gutenberg/pull/30554)) - RichText: Fix arrow navigation around emoji. ([30206](https://github.com/WordPress/gutenberg/pull/30206)) - Search block: Fix alignment issues. ([30444](https://github.com/WordPress/gutenberg/pull/30444)) - Site Logo: Delete sitelogo option when custom logo does not exist or was removed.( [30427](https://github.com/WordPress/gutenberg/pull/30427)) * Block List: Fix mover position in the docked toolbar. ([30242](https://github.com/WordPress/gutenberg/pull/30242)) * Code Editor: Revert save editors value on change ([#27717](https://github.com/WordPress/gutenberg/pull/27717)).( [30524](https://github.com/WordPress/gutenberg/pull/30524)) * Post Editor: - Avoid focus attempt on a non-existent post title in code editor. ([29922](https://github.com/WordPress/gutenberg/pull/29922)) - Fix the post author selector for contributor roles. ([30218](https://github.com/WordPress/gutenberg/pull/30218)) * Gutenberg PluginPlugin A 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.: Ensure that plugin does not error with older versions of WordPress. ([30230](https://github.com/WordPress/gutenberg/pull/30230)) * Inner blocks: Memoize allowedBlocks to prevent needlessly updating settings. ( [30311](https://github.com/WordPress/gutenberg/pull/30311)) * Server side renderer: Fix errors in template part editor context. ([29246](https://github.com/WordPress/gutenberg/pull/29246)) * Writing Flow: - Fix copy pasting non textual blocks. ([30225](https://github.com/WordPress/gutenberg/pull/30225)) - Fix horizontal caret placing for empty editable with placeholder. ([30463](https://github.com/WordPress/gutenberg/pull/30463)) - Fix multi-selection copying in Safari. ([30202](https://github.com/WordPress/gutenberg/pull/30202)) * Site Editor: - Fix nested template parts. ([30416](https://github.com/WordPress/gutenberg/pull/30416)) - Fix media upload behaviour and error state. ([30436](https://github.com/WordPress/gutenberg/pull/30436)) - Select the block inspector top upon selection. ([30387](https://github.com/WordPress/gutenberg/pull/30387)) * Components: Stop matching autocompleter upon mismatch. ([30649](https://github.com/WordPress/gutenberg/pull/30649)) ### APIs: * Add padding server-side block support. ([30332](https://github.com/WordPress/gutenberg/pull/30332)) * Remove small APIs deprecated in WordPress 5.2. ([30283](https://github.com/WordPress/gutenberg/pull/30283)) * Block Patterns: Remove `scope` from Query patterns and introduce `blockTypes`.( [30471](https://github.com/WordPress/gutenberg/pull/30471)) ### Experiments * Customizer - Add customize widgets inserter. ([29549](https://github.com/WordPress/gutenberg/pull/29549)) - Add Legacy Widget block. ([30321](https://github.com/WordPress/gutenberg/pull/30321)) - Fix adding blocks in the widgets customizer. ([30221](https://github.com/WordPress/gutenberg/pull/30221)) * Navigation Editor and Block - Apply mover tweaks to navigation and widgets. ([30284](https://github.com/WordPress/gutenberg/pull/30284)) - Add src/navigation-link/index to side effect whitelist. ([30200](https://github.com/WordPress/gutenberg/pull/30200)) - Add post format variation to navigation link block. ([30403](https://github.com/WordPress/gutenberg/pull/30403)) - Avoid creating a new array/object on every render. ([30374](https://github.com/WordPress/gutenberg/pull/30374)) - De-emphasize “Link” block. ([30172](https://github.com/WordPress/gutenberg/pull/30172)) - Fix arrow inheritance, polish. ([30287](https://github.com/WordPress/gutenberg/pull/30287)) - Fix hardcoded color in navigation submenu icon. ([30385](https://github.com/WordPress/gutenberg/pull/30385)) - Fix Navigation Link block constantly updating its inner block list settings.( [30274](https://github.com/WordPress/gutenberg/pull/30274)) - Fix navigation link block dragging error. ([30219](https://github.com/WordPress/gutenberg/pull/30219)) - Fix snackbar list component blocking clicks to UI it overlaps. ([30381](https://github.com/WordPress/gutenberg/pull/30381)) - Flip orientation of submenus that are towards the right of the viewport. ( [30342](https://github.com/WordPress/gutenberg/pull/30342)) - Indicate when a menu is deleted and show the menu switcher afterwards. ([29201](https://github.com/WordPress/gutenberg/pull/29201)) - Make the navigation placeholder clearer. ([30281](https://github.com/WordPress/gutenberg/pull/30281)) - Polish navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. submenus.( [30335](https://github.com/WordPress/gutenberg/pull/30335)) - Replace arrow with chevron. ([30180](https://github.com/WordPress/gutenberg/pull/30180)) - Save theme location on button click. ([30340](https://github.com/WordPress/gutenberg/pull/30340)) - Use same default implementation of __experimentalFetchLinkSuggestions in post, site, navigation, widget editor. ([29993](https://github.com/WordPress/gutenberg/pull/29993)) * Widgets Editor - Add manage with live preview link. ([29839](https://github.com/WordPress/gutenberg/pull/29839)) - Handle when $instance is empty and use str_replace instead of sprintf in the Widget block. ([30217](https://github.com/WordPress/gutenberg/pull/30217)) - Iterate on Legacy Widget block. ([29960](https://github.com/WordPress/gutenberg/pull/29960)) ### Documentation * Handbook: - Add description for `templateParts` in theme jsonJSON JSON, 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.. ([30118](https://github.com/WordPress/gutenberg/pull/30118)) - Add instructions for finding attributes for use in templates. ([30258](https://github.com/WordPress/gutenberg/pull/30258)) - Added a practical example of adding a component to the sidebarSidebar A 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.. ([30379](https://github.com/WordPress/gutenberg/pull/30379)) - Clarify what is meant by “block wrapper”. ([30315](https://github.com/WordPress/gutenberg/pull/30315)) - Fix broken links to typescript documentation. ([30188](https://github.com/WordPress/gutenberg/pull/30188)) - Fix code snippet for disabling the block directory. ([30365](https://github.com/WordPress/gutenberg/pull/30365)) - Fix formatting. ([30309](https://github.com/WordPress/gutenberg/pull/30309)) - Fix typos in block-controls-toolbar-and-sidebar.md. ([30513](https://github.com/WordPress/gutenberg/pull/30513)) - Rename, changed URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org Link. ([30483](https://github.com/WordPress/gutenberg/pull/30483)) - Rich Text: Add section for disabling specific format types. ([29383](https://github.com/WordPress/gutenberg/pull/29383)) - Updated documentation to reflect the output created currently by npx wordpress/ create-block gutenpride. ([30353](https://github.com/WordPress/gutenberg/pull/30353)) - Update feature deprecation guide. ([30220](https://github.com/WordPress/gutenberg/pull/30220)) * Packages: - Api-fetch: Fix example code for apiFetch middlewares. ([30534](https://github.com/WordPress/gutenberg/pull/30534)) - Block supports: Fix typos in layout supports comment. ([30537](https://github.com/WordPress/gutenberg/pull/30537)) - Block Editor: Fix block-editor typo. ([30401](https://github.com/WordPress/gutenberg/pull/30401)) - Components: * Remove references to __experimental* in the DateTimePicker component documentation.( [29322](https://github.com/WordPress/gutenberg/pull/29322)) * Update CustomSelectControl component README.md. ([29854](https://github.com/WordPress/gutenberg/pull/29854)) * docgen: - Components: Add types to Draggable. ([29792](https://github.com/WordPress/gutenberg/pull/29792)) - Add types to clean-node-list. ([30412](https://github.com/WordPress/gutenberg/pull/30412)) - Add types progressively to dom modules. ([30103](https://github.com/WordPress/gutenberg/pull/30103)) - Add types to phrasing-content. ([30102](https://github.com/WordPress/gutenberg/pull/30102)) - Export all types from api-fetch. ([30539](https://github.com/WordPress/gutenberg/pull/30539)) - Fix arrow functions and TS index module support. ([30028](https://github.com/WordPress/gutenberg/pull/30028)) - deprecated: Export DeprecatedOptions to align with DefinitelyTyped. ([30677](https://github.com/WordPress/gutenberg/pull/30677)) - api-fetch: Align exported type names with DefinitelyTyped types. ([30570](https://github.com/WordPress/gutenberg/pull/30570)) ### Code Quality * Block Editor: Use proper insertion point for drop. ([29933](https://github.com/WordPress/gutenberg/pull/29933)) * Block Library: Fix Post Excerpt warnings for RichText in inline containers. ( [30498](https://github.com/WordPress/gutenberg/pull/30498)) * Components: Simplify ScrollLock, adding types. ([29634](https://github.com/WordPress/gutenberg/pull/29634)) * Gutenberg Plugin: - Prettify YAML scripts. ([30409](https://github.com/WordPress/gutenberg/pull/30409)) - Remove deprecations planned for 10.3 release. ([30417](https://github.com/WordPress/gutenberg/pull/30417)) - Update the `objectFitPolyfill` vendor library. ([30507](https://github.com/WordPress/gutenberg/pull/30507)) * PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Coding Standards fixes. ([30346](https://github.com/WordPress/gutenberg/pull/30346)) ### Tools * Add `/packages/stylelint-config` to `CODEOWNERS`. ([30264](https://github.com/WordPress/gutenberg/pull/30264)) * Build: Ensure non-JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. changes are processed in the watch mode. ([30343](https://github.com/WordPress/gutenberg/pull/30343)) * Testing: - Added end-to-end tests for navigation menu name editor. ([29774](https://github.com/WordPress/gutenberg/pull/29774)) - GHA workflow improvements when setting up NodeJS. ([29078](https://github.com/WordPress/gutenberg/pull/29078)) - Include NodeJS version in the cache key. ([30512](https://github.com/WordPress/gutenberg/pull/30512)) - Remove button from forbidden elements. ([30223](https://github.com/WordPress/gutenberg/pull/30223)) - Remove cache `restore-keys`. ([30510](https://github.com/WordPress/gutenberg/pull/30510)) - Skip flaky end-to-end tests. ([30344](https://github.com/WordPress/gutenberg/pull/30344)) ## 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 10.4 | 5.94s | 35.14ms | | Gutenberg 10.3 | 5.98s | 32.58ms | | WordPress 5.7 | 5.05s | 31.34ms | Kudos to all the contributors that helped with the release! 👏 _Thanks [@youknowriad](https://profiles.wordpress.org/youknowriad/) for managing the release and [@critterverse](https://profiles.wordpress.org/critterverse/) for helping with the release post assets._ [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#editor](https://make.wordpress.org/core/tag/editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#gutenberg-new](https://make.wordpress.org/core/tag/gutenberg-new/) [ ](https://profiles.wordpress.org/andraganescu/) [Andrei Draganescu](https://profiles.wordpress.org/andraganescu/) 6:09 pm _on_ April 14, 2021 Tags: [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-summary ( 185 )](https://make.wordpress.org/core/tag/core-editor-summary/), [gutenberg ( 547 )](https://make.wordpress.org/core/tag/gutenberg/)    # 󠀁[Editor chat summary: 14 April, 2021](https://make.wordpress.org/core/2021/04/14/editor-chat-summary-14-april-2021/)󠁿 This post summarizes the weekly editor chat meeting ([agenda here](https://make.wordpress.org/core/2021/04/12/editor-chat-agenda-14-april-2021/)) held on [2021-04-14 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210414T1400) in [Slack](https://wordpress.slack.com/archives/C02QB2JS7/p1618408867340300). Moderated by [@andraganescu](https://profiles.wordpress.org/andraganescu/). ## GutenbergGutenberg The 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/](https://wordpress.org/gutenberg/)󠁿 10.4 release. * [@youknowriad](https://profiles.wordpress.org/youknowriad/) shared that the release post will be coming shortly (later today or tomorrow). It’s a release with a lot of work related to FSE, FSE Blocks, editor/frontend parity and many other updates. ## Full Site Editing Scope for WP5.8 The [post](https://make.wordpress.org/core/2021/04/08/full-site-editing-scope-for-wp5-8/) was shared during the chat and attention directed towards the outline of the 5.8 plans for FSE, and [@annezazu](https://profiles.wordpress.org/annezazu/) shared that there is a new [call for testing](https://make.wordpress.org/test/2021/04/14/fse-program-testing-call-5-query-quest/) available. Also we now have a board with [WordPress 5.8 FSE Must Haves](https://github.com/WordPress/gutenberg/projects/55). ## Monthly Priorities & Key Project Updates **Global Styles** [@nosolosw](https://profiles.wordpress.org/nosolosw/) shared in his GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) tracking issue: Landed: * Parts of theme.jsonJSON JSON, 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. with elements [PR:29891](https://github.com/WordPress/gutenberg/issues/29891) * preparations to make changes easier PR:[30801](https://github.com/WordPress/gutenberg/pull/30801) PR:[30610](https://github.com/WordPress/gutenberg/pull/30610) * i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/2021/page/42/?output_format=md#l10n). Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. process: make it not depend on a particular path [PR:30604](https://github.com/WordPress/gutenberg/pull/30604) * add mechanism to migrate from a v0 schema to the latest [PR:30600](https://github.com/WordPress/gutenberg/pull/30600) * clean-ups [PR:30605](https://github.com/WordPress/gutenberg/pull/30605) [PR:30612](https://github.com/WordPress/gutenberg/pull/30612) * border radius for the button blockBlock Block 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. [PR:30194](https://github.com/WordPress/gutenberg/pull/30194) * font size & font family for the button block [PR:30394](https://github.com/WordPress/gutenberg/pull/30394) * colors for the verse block [PR:27736](https://github.com/WordPress/gutenberg/pull/27736) * border radius for the search block [PR:30227](https://github.com/WordPress/gutenberg/pull/30227) Ongoing * theme.json with elements [Issue:29891](https://github.com/WordPress/gutenberg/issues/29891) * extract sanitization method [PR:30809](https://github.com/WordPress/gutenberg/pull/30809) * changes to shape [PR:30541](https://github.com/WordPress/gutenberg/pull/30541) * bugfixes [PR:30830](https://github.com/WordPress/gutenberg/pull/30830) * block supports: add new style properties: border-color, border-styles, border- width [PR:30124](https://github.com/WordPress/gutenberg/pull/30124) **Mobile team updates** [@chipsnyder](https://profiles.wordpress.org/chipsnyder/) shared the following updates: Landed * Generic embed block behind the DEV flag, actual functionality in progress * Interim dual-license license in place ([PR:30383](https://github.com/WordPress/gutenberg/pull/30383)) * Error notice improvements ([PR:30383](https://github.com/WordPress/gutenberg/pull/30273)) * Various fixes  In Progress: * Dual licensing Gutenberg: planning to merge [PR with interim license](https://github.com/WordPress/gutenberg/pull/30383) this week * Global Style Support ([PR:29969](https://github.com/WordPress/gutenberg/pull/29969)) * Reusable blocks * Search block * Adding search to the block inserter * Embed block * Simplification of media insertion flow * Slash inserter ([PR:29772](https://github.com/WordPress/gutenberg/pull/29772)) **Block based widgets and navigation editors** [@andraganescu](https://profiles.wordpress.org/andraganescu/) shared some updates: For the Block based WidgetWidget A 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. Editor the main focus these days is[ improving the performance ](https://github.com/WordPress/gutenberg/pull/30654) of the block editor in the customizerCustomizer Tool 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. and moving our attention to testing the level of[ back compat](https://github.com/WordPress/gutenberg/pull/30709) existing and achievable. **Navigation block** [@andraganescu](https://profiles.wordpress.org/andraganescu/), [@joen](https://profiles.wordpress.org/joen/) and [@mkaz](https://profiles.wordpress.org/mkaz/) shared updates: * Progress continues, responsive menus expected this week * One notable merge since last is converting Page List block to menu items * Justification controls added to vertical * Working through extensibility for allowing additional block types in Social and Navigation blocks * preparing for patterns. Notably, looking at [submenu colors](https://github.com/WordPress/gutenberg/pull/30831), [small glitches](https://github.com/WordPress/gutenberg/pull/30824), [removing menu item padding when there’s no background](https://github.com/WordPress/gutenberg/pull/30805). The last one should open up a great deal of nice minimalist patterns. * ongoing discussion about  [the block’s markup](https://github.com/WordPress/gutenberg/pull/30551) and the work on adding a Links List block **Update on the post schedule component** [@retrofox](https://profiles.wordpress.org/retrofox/) shared an update about a couple of enhancements in the post-schedule component. Now, it shows calendar events with a small blue bullet. Events are scheduled and published posts. ## Task Coordination [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) * Landed patterns suggestion for transforming simple selected blocks (no InnerBlocks)( [PR:30469](https://github.com/WordPress/gutenberg/pull/30469)) * Add active block variation information in Block Parent Selector (PR:30731) [@youknowriad](https://profiles.wordpress.org/youknowriad/) I’m iterating on the “template mode” of the post editor. (Creating and editing block templates in the post editor) [@joen](https://profiles.wordpress.org/joen/) In addition to the navigation block, I had these two, one is a work in progress, the other could use your eyes: * [showing one appender at time](https://github.com/WordPress/gutenberg/pull/30833) * [making the appender not jump when you click it the first time](https://github.com/WordPress/gutenberg/pull/30656). [@mamaduka](https://profiles.wordpress.org/mamaduka/) I mainly worked on enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. issues: * Add “Most used terms” section to [term selector](https://github.com/WordPress/gutenberg/pull/30598). * Add block title to [block switcher label](https://github.com/WordPress/gutenberg/pull/30808). * Add the “Reset” button to [Layout controls](https://github.com/WordPress/gutenberg/pull/30828). * Add [uploading state](https://github.com/WordPress/gutenberg/pull/30837) to video block. * I also tried to track down, unsuccessfully, the Safari browser issues. [@annezazu](https://profiles.wordpress.org/annezazu/) Working on all things FSE Outreach Program — responding to feedback for the fourth call for testing/opening lots of issues, [held a hallway hangout about FSE](https://make.wordpress.org/test/2021/04/08/hallway-hangout-discussion-on-full-site-editing-issues-prs-designs-8-april/), still testing FSE everyday, and am going to ship a fifth call for testing today with a summary post of the fourth call for testing to follow later this week. ## Open Floor ### Contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of 󠀁[https://make.wordpress.org/](https://make.wordpress.org/)󠁿 There are many teams that people can participate in, each with a different focus. 󠀁[https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)󠁿 at Yoast [@poena](https://profiles.wordpress.org/poena/) announced that last week there was a contributor day at Yoast with user testing and code contributions to FSE. A large amount of feedback issues were open and some that are already being solved. ### Issues and PRs needing eyes and contributions * Discussion: documentation handbook plans for site editing and beyond: [Issue:30637](https://github.com/WordPress/gutenberg/issues/30637) * FSE: Finalizing the name and menu item placement [Issue: 29630](https://github.com/WordPress/gutenberg/issues/29630) * Post and site editor title placement: [Issue:27093](https://github.com/WordPress/gutenberg/issues/27093) * Shared block editor settings PR, which requires some updates to the existing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher hooksHooks In 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. and could use some eyes for sanity checks and reviews [PR: 1118](https://github.com/WordPress/wordpress-develop/pull/1118) ### Status of the existing Block Template APIAPI An 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. [@itsjusteileen](https://profiles.wordpress.org/itsjusteileen/) asked about the future of the Block Template API in the context of FSE developments and noted that the code [examples in the handbook](https://developer.wordpress.org/block-editor/reference-guides/block-api/block-templates/#api) don’t work anymore. It doesn’t appear that the block template API will go away and we should have some issues open if the documentation is outdated or the API broken. ### Feedback needed on several widgets/blocks discussions * [a discussion](https://github.com/WordPress/gutenberg/issues/15916) about allowing users to insert a Classic Block in a SidebarSidebar A 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. on the Widgets (betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.) screen * a discussion about [reconstructing ](https://github.com/WordPress/gutenberg/issues/26012) Widgets Screen to use the Customize API. This is a fancy way to say that we should or could remove the standalone editor as the new block based widgets editor lands in a future WP release. * [a question](https://github.com/WordPress/gutenberg/issues/26154): assuming the block based widgets editor is an opt out feature what is the preferred way to opt out ### Design process for the widgets updates [@Anthony](https://profiles.wordpress.org/anthony/) Nolan brought up a question around where can one find the process that led up to the current state in the block based widgets editor project, and was guided towards going through closed issues such as [this one](https://github.com/WordPress/gutenberg/issues/27343#issuecomment-765644623) or [this one](https://github.com/WordPress/gutenberg/issues/26900), which cover updating the customizer or look at the open project to see how the stand alone [widgets editor](https://github.com/WordPress/gutenberg/projects/27) progresses. [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 3:42 pm _on_ April 14, 2021 Tags: [make.wordpress.org/test ( 29 )](https://make.wordpress.org/core/tag/make-wordpress-orgtest/), [p2-xpost ( 213 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: FSE Program Testing Call #5: Query Quest](https://make.wordpress.org/core/2021/04/14/xpost-fse-program-testing-call-5-query-quest/)󠁿 X-comment from [+make.wordpress.org/test](https://make.wordpress.org/test/): Comment on [FSE Program Testing Call #5: Query Quest](https://make.wordpress.org/test/2021/04/14/fse-program-testing-call-5-query-quest/#comment-1489) [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 10:21 pm _on_ April 13, 2021 Tags: [5.7.1 ( 20 )](https://make.wordpress.org/core/tag/5-7-1/), [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/), [dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/)    # 󠀁[Dev Chat Agenda for April 14, 2021](https://make.wordpress.org/core/2021/04/13/dev-chat-agenda-for-april-14-2021/)󠁿 Here is the agenda for this week’s meetings to occur at the following times: [April 14, 2021 at 5:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210414T0500) and [April 14, 2021 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210414T2000). ## Release Announcements * [5.7.1 maintenance release](https://core.trac.wordpress.org/tickets/minor/workflow) is scheduled to be released on April 14 * [Full Site Editing Scope for WP5.8](https://make.wordpress.org/core/2021/04/08/full-site-editing-scope-for-wp5-8/) * [Early test scrub for WordPress 5.8](https://make.wordpress.org/core/2021/04/12/early-test-scrub-for-wordpress-5-8-2/) * [Gutenberg 10.4 RC1 is available](https://github.com/WordPress/gutenberg/releases/tag/v10.4.0-rc.1) ## Blogblog (versus network, site) Post Highlights * [[[A Week in Core – April 12, 2021](https://make.wordpress.org/core/2021/04/12/a-week-in-core-april-12-2021/) * [What’s next in Gutenberg? (April 2021)](https://make.wordpress.org/core/2021/04/08/whats-next-in-gutenberg-april-2021/) * [Recent Build/Test Tool changes and GitHub Actions update](https://make.wordpress.org/core/2021/04/08/recent-build-test-tool-changes-and-github-actions-update/) ## Blog posts that need feedback * [Follow up to the native TypeScript proposal](https://make.wordpress.org/core/2021/04/09/follow-up-to-the-native-typescript-proposal/) * [Feedback | Full Site Editing in WP5.8](https://make.wordpress.org/updates/2021/04/09/feedback-full-site-editing-in-wp5-8/) ## 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 our standard list 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](https://wordpress.slack.com/messages/C02RQBWTW) channel. To join the meeting, you’ll need an account on the [Making WordPress Slack](https://make.wordpress.org/chat/). [#5-7-1](https://make.wordpress.org/core/tag/5-7-1/), [#5-8](https://make.wordpress.org/core/tag/5-8/), [#agenda](https://make.wordpress.org/core/tag/agenda/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/) 4:02 pm _on_ April 13, 2021 Tags: [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[CSS Chat Summary: 08 April 2021](https://make.wordpress.org/core/2021/04/13/css-chat-summary-08-april-2021/)󠁿 [The meeting took place here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1617915794266300). [@notlaura](https://profiles.wordpress.org/notlaura/) facilitated and [@danfarrow](https://profiles.wordpress.org/danfarrow/) wrote up these notes. ## Housekeeping * Our next bugbug A 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. scrub will be on 22 April at 8pm UTC. If anyone is interested in leading it please let us know in the [#core-css](https://make.wordpress.org/core/tag/core-css/) channel ## Discussion: CSSCSS Cascading Style Sheets. deprecation path * [The issue initially came up via this ticket](https://github.com/WordPress/gutenberg/issues/28664) and will grow as we start to introduce custom properties into the WP Adminadmin( and super admin) CSS * [@helen](https://profiles.wordpress.org/helen/) [previously outlined an approach in this post](https://helen.wordpress.com/2012/12/15/can-markup-and-css-be-backwards-compatible/)– deprecated CSS would be moved to a `deprecated` file that plugins can still optionally enqueue. It would be helpful if it could run standalone, and if an example of how to implement and run it could be provided e.g. as a GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) Action workflow * Deprecated CSS would generally be at the selector level * [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) provided the recent examples of `.icon16` ([raised in #35717](https://core.trac.wordpress.org/ticket/35717)) and `.wp-ui-text-icon` * **We agreed that `.icon16` would be a good deprecation candidate to test the process** * [@notlaura](https://profiles.wordpress.org/notlaura/) suggested adding deprecated selectors to a disallowed list in stylelint, and a PostCSS script to build the` deprecated.css` stylesheet. PostCSS & stylelint could share the same config file to track deprecated selectors * [@Ahmed](https://profiles.wordpress.org/ahmed/) Saeed suggested adding a deprecation notice as a CSS custom property which would be discoverable in dev tools * [@ryelle](https://profiles.wordpress.org/ryelle/) added that we would probably want multiple ways to flag deprecated CSS and @tellthemachines agreed it would need to be part of the build process * [@notlaura](https://profiles.wordpress.org/notlaura/) suggested a `deprecated- with-warnings.css` file which is enqueued if `WP_DEBUG` is on * [@ryelle](https://profiles.wordpress.org/ryelle/) clarified the two parts of the problem: identifying the deprecated CSS, and developing external tools for pluginPlugin A 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. developers ### Next step * The next step would be writing a TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. outlining the solution & raising it in dev chat * @tellthemachines offered to write the ticket ## Discussion: CSS naming and usage conventions for JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. targeting (󠀁[#40686](https://core.trac.wordpress.org/ticket/40686)󠁿) * The intention is to establish a convention for naming CSS classes which are intended for use with JavaScriptJavaScript JavaScript 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](https://www.javascript.com/) * There was some discussion to clarify the problem, but in relation to CSS deprecation we need to ensure we’re not deprecating CSS classes that are used by JavaScript * We agreed that a `js-` prefix would clarify that a particular classname is intended for JavaScript interaction ## Open Floor + CSS Link Share * **CSS Audit ([#49582](https://core.trac.wordpress.org/ticket/49582)) **[@ryelle](https://profiles.wordpress.org/ryelle/) has updated the readme & started the process of transferring the repo over to the WordPress org * **Custom property naming** [@ryelle](https://profiles.wordpress.org/ryelle/) has started drafting a make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post about the custom property naming discussions which she’ll share in the channel before posting * [@danfarrow](https://profiles.wordpress.org/danfarrow/) reminded us that April 09 is the annual [CSS Naked Day](https://css-naked-day.github.io/)! Thanks everyone! [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/paaljoachim/) [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/) 9:54 pm _on_ April 12, 2021 Tags: [agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/), [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-agenda ( 189 )](https://make.wordpress.org/core/tag/core-editor-agenda/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/)    # 󠀁[Editor Chat Agenda: 14 April 2021](https://make.wordpress.org/core/2021/04/12/editor-chat-agenda-14-april-2021/)󠁿 Facilitator and notetaker: @andraganescu This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, April 14, 2021, 0](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210414T16&p1=187&ah=1) [4:00 PM GMT+1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210331T10&p1=2157&ah=1). _This meeting is held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)._ * GutenbergGutenberg The 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/](https://wordpress.org/gutenberg/) 10.4 release. * [Full Site Editing Scope for WP5.8](https://make.wordpress.org/core/2021/04/08/full-site-editing-scope-for-wp5-8/) * [Monthly Plan for April 2021](https://make.wordpress.org/core/2021/04/08/whats-next-in-gutenberg-april-2021/) and key project updates: - Global Styles. * - BlockBlock Block 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. based WidgetWidget A 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. Editor. - Navigation block. - Full Site Editing. * 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 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](https://make.wordpress.org/core/tag/agenda/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-agenda](https://make.wordpress.org/core/tag/core-editor-agenda/), [#meeting](https://make.wordpress.org/core/tag/meeting/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 9:11 pm _on_ April 12, 2021 Tags: [5.7.1 ( 20 )](https://make.wordpress.org/core/tag/5-7-1/), [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/) # 󠀁[A Week in Core – April 12, 2021](https://make.wordpress.org/core/2021/04/12/a-week-in-core-april-12-2021/)󠁿 Welcome back to a new issue of _Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress._. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between April 5 and April 12, 2021. * 26 commits * 42 contributors * 54 tickets created * 9 tickets reopened * 45 tickets closed Reminder: WordPress 5.7.1 is [planned for April 14, 2021](https://make.wordpress.org/core/2021/03/22/wordpress-5-7-1-maintenance-release-schedule/). The [release candidate](https://make.wordpress.org/core/2021/04/07/wordpress-5-7-1-rc-1/) is available for testing. Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the [Trac timeline for the period above](https://core.trac.wordpress.org/timeline?from=04%2F12%2F2021&daysback=7&authors=&ticket=on&sfp_email=&sfph_mail=&update=Update). The following is a summary of commits, organized by component. ## Code changes ### Administration * Update various background colors for increased contrast – [#52760](https://core.trac.wordpress.org/ticket/52760) ### Build/Test Tools * Remove remaining Travis CI references – [#52161](https://core.trac.wordpress.org/ticket/52161), [#52666](https://core.trac.wordpress.org/ticket/52666) * Prevent PHPUnit tests on `push` for forks/private mirrors – [#52983](https://core.trac.wordpress.org/ticket/52983) * Update dependencies in default themes – [#52624](https://core.trac.wordpress.org/ticket/52624) * Update development dependencies from WP packages – [#52991](https://core.trac.wordpress.org/ticket/52991) * Revert `package-lock.json` change in [[50682]](https://core.trac.wordpress.org/changeset/50682)– [#52768](https://core.trac.wordpress.org/ticket/52768) * Update some dependencies – [#52624](https://core.trac.wordpress.org/ticket/52624) ### Bundled Themes * Update the “Tested up to” value – [#52859](https://core.trac.wordpress.org/ticket/52859) * Twenty Twenty-One: Rebuild IE specific editor stylesheet – [#52981](https://core.trac.wordpress.org/ticket/52981), [#52702](https://core.trac.wordpress.org/ticket/52702) ### Coding Standards * Rewrite a fragment in `request_filesystem_credentials()` for clarity and to avoid repetition – [#52627](https://core.trac.wordpress.org/ticket/52627) * Use strict comparison in `wp-admin/includes/file.php` – [#52627](https://core.trac.wordpress.org/ticket/52627) * Simplify the check for parent terms in `export_wp()` – [#52627](https://core.trac.wordpress.org/ticket/52627) * Use strict comparison in `wp-admin/includes/credits.php` – [#52627](https://core.trac.wordpress.org/ticket/52627) * Use strict comparison in `wp-admin/includes/comment.php` – [#52627](https://core.trac.wordpress.org/ticket/52627) * Remove unnecessary `unset()` calls in `WP_Importer` methods – [#52996](https://core.trac.wordpress.org/ticket/52996) * Use strict comparison in `wp-admin/includes/dashboard.php` – [#52627](https://core.trac.wordpress.org/ticket/52627) * Give a variable in `wp-admin/themes.php` a more meaningful name – [#52627](https://core.trac.wordpress.org/ticket/52627) ### Customize * Set `playsinline` attribute for custom headerHeader The 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. videos – [#50111](https://core.trac.wordpress.org/ticket/50111) ### Editor * Use a consistent way to retrieve post ID on Edit Post screens – [#52995](https://core.trac.wordpress.org/ticket/52995) * Ensure wordpress/inteface package is listed as a dependency – [#52991](https://core.trac.wordpress.org/ticket/52991) ### Login and Registration * Check if `$_GET['login']` is set before using it in `wp-login.php` – [#52980](https://core.trac.wordpress.org/ticket/52980) ### Media * Do not lazy load hidden images or embeds – [#52768](https://core.trac.wordpress.org/ticket/52768) ### Options, MetaMeta Meta 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 * Update default color scheme swatch to match CSSCSS Cascading Style Sheets. changes– [#52750](https://core.trac.wordpress.org/ticket/52750) ### REST APIREST API The 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/](https://developer.wordpress.org/rest-api/)󠁿 * Move the `rest_jsonp_enabled` filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. before setting the Content-Type header – [#52691](https://core.trac.wordpress.org/ticket/52691) ### Site Health * Reduce false reports of HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. failures – [#52783](https://core.trac.wordpress.org/ticket/52783) ### Themes * Remove unused code fragment from `wp-admin/themes.php` – [#53005](https://core.trac.wordpress.org/ticket/53005) ## Props **Thanks to the 42 people who contributed to WordPress Core on Trac last week:** [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (3), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 3), [@mukesh27](https://profiles.wordpress.org/mukesh27/) (3), [@johnbillion](https://profiles.wordpress.org/johnbillion/)( 2), [@TimothyBlynJacobs](https://profiles.wordpress.org/timothyblynjacobs/) (2), [@ocean90](https://profiles.wordpress.org/ocean90/) (2), [@ravipatel](https://profiles.wordpress.org/ravipatel/)( 2), [@klevyke](https://profiles.wordpress.org/klevyke/) (1), [@annalamprou](https://profiles.wordpress.org/annalamprou/)( 1), [@AnotherDave](https://profiles.wordpress.org/anotherdave/) (1), [@ayeshrajans](https://profiles.wordpress.org/ayeshrajans/)( 1), [@bobbingwide](https://profiles.wordpress.org/bobbingwide/) (1), [@Clorith](https://profiles.wordpress.org/clorith/)( 1), [@dragongate](https://profiles.wordpress.org/dragongate/) (1), [@geoffrey1963](https://profiles.wordpress.org/geoffrey1963/)( 1), [@eatsleepcode](https://profiles.wordpress.org/eatsleepcode/) (1), [@gab81](https://profiles.wordpress.org/gab81/)( 1), [@ninetyninew](https://profiles.wordpress.org/ninetyninew/) (1), [@Ipstenu](https://profiles.wordpress.org/ipstenu/)( 1), [@k3nsai](https://profiles.wordpress.org/k3nsai/) (1), [@mmuyskens](https://profiles.wordpress.org/mmuyskens/)( 1), [@nicegamer7](https://profiles.wordpress.org/nicegamer7/) (1), [@pwallner](https://profiles.wordpress.org/pwallner/)( 1), [@ryelle](https://profiles.wordpress.org/ryelle/) (1), [@swissspidy](https://profiles.wordpress.org/swissspidy/)( 1), [@desrosj](https://profiles.wordpress.org/desrosj/) (1), [@melchoyce](https://profiles.wordpress.org/melchoyce/)( 1), [@dd32](https://profiles.wordpress.org/dd32/) (1), [@rkradadiya](https://profiles.wordpress.org/rkradadiya/)( 1), [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) (1), [@jrf](https://profiles.wordpress.org/jrf/)( 1), [@rachelbaker](https://profiles.wordpress.org/rachelbaker/) (1), [@kebbet](https://profiles.wordpress.org/kebbet/)( 1), [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) (1), [@audrasjb](https://profiles.wordpress.org/audrasjb/)( 1), [@fabianpimminger](https://profiles.wordpress.org/fabianpimminger/) (1), [@flixos90](https://profiles.wordpress.org/flixos90/)( 1), [@jonkastonka](https://profiles.wordpress.org/jonkastonka/) (1), [@joyously](https://profiles.wordpress.org/joyously/)( 1), [@SirStuey](https://profiles.wordpress.org/sirstuey/) (1), [@satrancali](https://profiles.wordpress.org/satrancali/)( 1), and [@Toru](https://profiles.wordpress.org/toru/) (1). **Please welcome our 17 (!!) new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. [https://core.trac.wordpress.org](https://core.trac.wordpress.org) of the week ♥️[@klevyke](https://profiles.wordpress.org/klevyke/), [@annalamprou](https://profiles.wordpress.org/annalamprou/), [@AnotherDave](https://profiles.wordpress.org/anotherdave/), [@dragongate](https://profiles.wordpress.org/dragongate/), [@geoffrey1963](https://profiles.wordpress.org/geoffrey1963/), [@eatsleepcode](https://profiles.wordpress.org/eatsleepcode/), [@gab81](https://profiles.wordpress.org/gab81/), [@ninetyninew](https://profiles.wordpress.org/ninetyninew/), [@k3nsai](https://profiles.wordpress.org/k3nsai/), [@mmuyskens](https://profiles.wordpress.org/mmuyskens/), [@nicegamer7](https://profiles.wordpress.org/nicegamer7/), [@pwallner](https://profiles.wordpress.org/pwallner/), [@rkradadiya](https://profiles.wordpress.org/rkradadiya/), [@fabianpimminger](https://profiles.wordpress.org/fabianpimminger/), [@jonkastonka](https://profiles.wordpress.org/jonkastonka/), [@SirStuey](https://profiles.wordpress.org/sirstuey/), and [@satrancali](https://profiles.wordpress.org/satrancali/). **Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 11), [@desrosj](https://profiles.wordpress.org/desrosj/) (5), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/)( 4), [@ocean90](https://profiles.wordpress.org/ocean90/) (2), [@gziolo](https://profiles.wordpress.org/gziolo/)( 2), [@rachelbaker](https://profiles.wordpress.org/rachelbaker/) (1), and [@ryelle](https://profiles.wordpress.org/ryelle/)( 1). [#5-7-1](https://make.wordpress.org/core/tag/5-7-1/), [#5-8](https://make.wordpress.org/core/tag/5-8/), [#week-in-core](https://make.wordpress.org/core/tag/week-in-core/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 9:08 pm _on_ April 12, 2021 Tags: [5.7.1 ( 20 )](https://make.wordpress.org/core/tag/5-7-1/), [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [core-auto-updates ( 37 )](https://make.wordpress.org/core/tag/core-auto-updates/), [dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Dev Chat meeting Summary – April 7, 2021](https://make.wordpress.org/core/2021/04/12/dev-chat-meeting-summary-april-7-2021/)󠁿 This is the weekly meetings summary of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.  team. The facilitator for this week’s chats was [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) at 05:00 UTC and [@francina](https://profiles.wordpress.org/francina/) at 20:00 UTC. Here is the [meeting agenda](https://make.wordpress.org/core/2021/04/06/dev-chat-agenda-for-april-7-2021/). [Link to 05:00 UTC devchat meeting on the core channel on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1617771900421600) [Link to 20:00 UTC devchat meeting on the core channel on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1617825626455700) ## Announcements & News ### Upcoming releases #### WordPress 5.7.1 In line with [the trial for consistent minor release leads for each major branch](https://make.wordpress.org/core/2021/03/16/trial-run-consistent-minor-release-squad-leaders-for-each-major-branch/), all the 5.7.x point releases will be led by [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/), with [@audrasjb](https://profiles.wordpress.org/audrasjb/) as deputy. Here is the expected 5.7.1 release schedule: * Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/2021/page/42/?output_format=md#alpha-beta).: Wednesday 7 April, 2021 around 23:00 UTC ([released](https://make.wordpress.org/core/2021/04/07/wordpress-5-7-1-rc-1/)) * Final release: Wednesday 14 April, 2021 around 23:00 UTC [@audrasjb](https://profiles.wordpress.org/audrasjb/) announced (and hosted) a new bugbug A 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. scrub right after the devchat. _Note: At the time this meeting recap is published, [WP 5.7.1 Release Candidate 1 is now available for testing](https://make.wordpress.org/core/2021/04/07/wordpress-5-7-1-rc-1/)._ #### WordPress 5.8 [@francina](https://profiles.wordpress.org/francina/) shared some blogposts worth reading, where a new, experimental, release cycle is proposed, and the early bug scrubs schedule is now available. * [5.8 Pre-planning](https://make.wordpress.org/core/2021/03/30/5-8-pre-planning/) * [Early Bug Schedule for 5.8](https://make.wordpress.org/core/2021/03/24/early-bug-schedule-for-5-8/) ### Core related blogblog (versus network, site) posts * [[[Gutenberg 10.3 released](https://make.wordpress.org/core/2021/04/02/whats-new-in-gutenberg-10-3-31-march/) * [[[5.7.1 maintenance release candidate](https://core.trac.wordpress.org/tickets/minor/workflow) is scheduled to be released at 2300 UTC on April 7th * [[[Early test scrub for WordPress 5.8](https://make.wordpress.org/core/2021/04/07/early-test-scrub-for-wordpress-5-8/) has been scheduled * [A Week in Core – April 5, 2021](https://make.wordpress.org/core/2021/04/05/a-week-in-core-april-5-2021/) * [Core Editor Improvement: Easier than ever to find the blocks you need](https://make.wordpress.org/core/2021/03/31/core-editor-improvement-easier-than-ever-to-find-the-blocks-you-need/) * [Did you know there is a new podcast in town?](https://wordpress.org/news/podcast/) [@annezazu](https://profiles.wordpress.org/annezazu/) shared that the [current FSE call for testing](https://make.wordpress.org/test/2021/03/25/fse-program-testing-call-4-building-a-restaurant-themed-header/) is now open for feedback until **April 12th** rather than April 8th. Hopefully, this gives people an extra weekend to chime in and share their experience. [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) pointed out that the first go/no go date for FSE in WP5.8 is next Tuesday. [@nalininonstopnewsuk](https://profiles.wordpress.org/nalininonstopnewsuk/) shared that it is possible share [FSE Call for Testing](https://wp.me/p4FYxH-1v0) on social and [FSE Call for Testing](https://www.linkedin.com/posts/make-wordpress-marketing-team_fse-program-testing-call-4-building-a-restaurant-activity-6782661638878183424-8WDE) on LinkedIn. [@francina](https://profiles.wordpress.org/francina/) shared this blog post from the Marketing Team: [Thoughts on Marketing, FSE, and What’s Next](https://make.wordpress.org/marketing/2021/03/30/thoughts-on-marketing-fse-and-whats-next/). It’s relevant to the current release, so please read and leave your feedback. ## Component maintainers updates **Build/Test Tools** ([@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)): Work has continued on backporting recent build and test tool improvements to the older branches still receiving security updates. See ticketticket Created for both bug reports and feature development on the bug tracker. [#52653](https://core.trac.wordpress.org/ticket/52653) for more details. A post is also upcoming on make/core. **Date/Time**, **General**, **I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/2021/page/42/?output_format=md#l10n). Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.**, **Permalinks** ([@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)): No major news this week. **Menus**, **Widgets**, **Upgrade/Install** ([@audrasjb](https://profiles.wordpress.org/audrasjb/)): No major news this week. **Site Health** ([@clorith](https://profiles.wordpress.org/clorith/)): The only ticket in milestone 5.7.1 was committed in time. [@francina](https://profiles.wordpress.org/francina/) also pointed out [the ticket she opened in Meta Trac concerning Component maintainers updates](https://meta.trac.wordpress.org/ticket/5463). In the past month she also reached out to the majority of the components and removed inactive maintainers. Right now there are quite a lot of [components](https://make.wordpress.org/core/components/) without maintainers. The attendees discussed about maintainers recruitment. If anyone is interested to help to maintain a component, [@audrasjb](https://profiles.wordpress.org/audrasjb/) pointed out that he would be happy to mentor/explain what he is doing on the few components he maintains. [@francina](https://profiles.wordpress.org/francina/) proposed an online meeting/Q&A, [like the casual online gatherings hosted by the community team](https://make.wordpress.org/community/handbook/virtual-events/overview-of-casual-online-gatherings/). ## Open floor [@paaljoachim](https://profiles.wordpress.org/paaljoachim/) asked what is the definition of what can and not not be included in a minor releaseMinor Release A 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.. [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) quoted the [Core team handbook](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-minor-versions/):“ A minor release is intended for bugfixes and enhancements that do not add new deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. files and are at the discretion of the release leadRelease Lead The community member ultimately responsible for the Release. with suggestions/input from component maintainers and committers.” [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) added that generally, minor releases are addressing regressions introduced in the latest release and some follow-up changes to new features, with occasional fixes for bugs from other recent releases, and occasional enhancements that the release leads feel are necessary. [#5-7-1](https://make.wordpress.org/core/tag/5-7-1/), [#5-8](https://make.wordpress.org/core/tag/5-8/), [#core-auto-updates](https://make.wordpress.org/core/tag/core-auto-updates/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/boniu91/) [Piotrek Boniu](https://profiles.wordpress.org/boniu91/) 7:00 pm _on_ April 12, 2021 Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [test ( 16 )](https://make.wordpress.org/core/tag/test/), [testing ( 25 )](https://make.wordpress.org/core/tag/testing/) # 󠀁[Early test scrub for WordPress 5.8](https://make.wordpress.org/core/2021/04/12/early-test-scrub-for-wordpress-5-8-2/)󠁿 In the previous week we didn’t run the test scrub. That’s why the agenda stays the same for this week. Early test scrub for WordPress 5.8 will take place on [2021-04-16 13:30](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210416T1330) in the [core-test](https://app.slack.com/client/T024MFP4J/C02RQBWTW) channel. We’ll do manual testing of the below tickets, making sure there are no regressions: [https://core.trac.wordpress.org/ticket/32579](https://core.trac.wordpress.org/ticket/32579) [https://core.trac.wordpress.org/ticket/52226](https://core.trac.wordpress.org/ticket/52226) [https://core.trac.wordpress.org/ticket/52521](https://core.trac.wordpress.org/ticket/52521) [https://core.trac.wordpress.org/ticket/52662](https://core.trac.wordpress.org/ticket/52662) [https://core.trac.wordpress.org/ticket/40570](https://core.trac.wordpress.org/ticket/40570) [https://core.trac.wordpress.org/ticket/39108](https://core.trac.wordpress.org/ticket/39108) **We’ll appreciate your participation and feedback!** **What you need** * WordPress environment * WordPress 5.8 alpha release, try the [WordPress Beta Tester plugin](https://wordpress.org/plugins/wordpress-beta-tester/)( choose the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as [trunk](https://make.wordpress.org/core/2021/page/42/?output_format=md#trunk).” channel and BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process./ RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/2021/page/42/?output_format=md#alpha-beta). Only” stream options) * Two of the tickets are not merged yet. To test them we’ll need to set up the Testing Environment by following the steps listed here – [https://meta.trac.wordpress.org/ticket/5581#comment:3](https://meta.trac.wordpress.org/ticket/5581#comment:3) ## How to apply a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a **diff**. A patch can be _applied_ to a codebase for testing. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker., for example `35449` ```wp-block-preformatted npm run grunt patch:35449 ``` How to fetch and then checkout a PR, for example, PR 828 ```wp-block-preformatted git fetch upstream pull/828/head:pr-828git checkout pr-828 ``` or for PR: ```wp-block-preformatted npm run grunt patch:https://github.com/WordPress/wordpress-develop/pull/828 ``` Check the handbook for more ways to [test patches](https://make.wordpress.org/core/handbook/testing/patch/). Looking forward to seeing you! [#5-8](https://make.wordpress.org/core/tag/5-8/), [#test](https://make.wordpress.org/core/tag/test/), [#testing](https://make.wordpress.org/core/tag/testing/) # Post navigation [← Older posts](https://make.wordpress.org/core/2021/page/43/?output_format=md) [Newer posts →](https://make.wordpress.org/core/2021/page/41/?output_format=md)