What’s New in Gutenberg? (23th January)

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/ 4.9 is a big milestone in terms for performance improvements for Gutenberg. It introduces a new asynchronous mode for blocks rendering improving the responsiveness of the editor.

The Documentation efforts are still on-going with three new tutorials leveraging the Format API, the Sidebar Plugins API and Post Meta Blocks as well as a number of improved README files for our UIUI User interface components.

In terms of developer experience, this release includes a lot of improvements to our e2e tests including support for aXe AccessibilityAccessibility Accessibility (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) testing.

4.9 🇦🇺

Performance

• Implement an async rendering mode for the data module updates.
• Avoid rerendering the block components when selecting a block.
• Improve the performance of isEditorEmptyPost selector (13% typing performance improvement).
• Data Module: Avoid persisting unchanged values.
• Update withSelect to use type-optimized isShallowEqual.
• Move data selection to event handlers (called only when necessary).
• Improve the initial rendering time by optimizing the withFilters Higher-order component.

Bug Fixes

• Fix RichText toolbar when using multiline=”li”.
• Correct the margin of the block icons in the inserter.
• Fix ampersand in post tags causing editor crash.
• Remove alignundefined class from gallery block edit markup.
• Disable the button to open the publish 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. if locked.
• Correct the default margin for buttons with icons.
• Keep the date floating when for posts with “pending” status.
• Fix using the EXIF title when uploading images.
• Fix font size picker on mobile.
• Fix z-index of the Reusable Block Inserter button.
• Fix autop behavior when a text is followed by a div.
• Fix warning when returning null from a data module generator.
• Announce the screen reader messages in the correct order in Safari.
• Check Post Type support in the options modal.

Enhancements

• Support customizing the table background colors.
• Support underlining text using the keyboard shortcut ctrl+U.
• Apply the editor styles to the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. Block Preview.
• Improve the color swatch selection indicator.
• Improve scrolling behavior in Fullscreen Mode in Edge.
• Remove deprecated embed providers.

• Refactor the alignements support in the Cover Block and the Categories Block.
• Code quality improvement to getBlockContentSchema
• Internationalize the excerpt documentation link.
• Improve pasting of quotes with citations.
• A11yAccessibility Accessibility (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)
  • Add a tooltip to the block list appender.
  • Improve the color contrast of the inserter shortcuts.
  • Remove the label from the Warning component’s menu.
• Add an option to overwrite the block in the Warning component.

Extensibility

• Support custom fetch handlers for wp.apiFetch.
• Support additional data passed to the mediaUpload utility.
• Add filterFilter Filters are one of the two types of 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. for the preview interstitial markup.
• Avoid appending empty query string in wp.url.addQueryArgs.
• Dispatch heartbeat events as hook actions to avoid the jQuery dependency.
• Support adding classnames to the plugins sidebar panels.
• Add a className to the parent page selector.

Documentation

• Add tutorials for
  • Creating sidebar plugins.
  • Using the Format API.
  • Creating meta blocks.
• Reorganize the tutorials page.
• Improve the UI component documentation:
  • The ButtonGroup component.
  • The IconButton component.
  • The SelectControl component.
  • The TextareaControl component.
  • The TabPanel component.
  • The Toolbar component.
  • The FormToggle component.
• Update the Gutenberg Release and the Repository Management docs.
• Add new section on scoping JS code.
• Use Block Editor instead of Gutenberg in the docs.
• Mention the Advanced Controls Panel in the design guidelines.
• Clarify the unregisterBlockStyle documentation.
• Clarify the difference between the button block and the button component.
• Scope 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/. ES5 code example.
• Fix incorrect code example.
• Clarify the deprecated APIs.
• Fix typos 1 2 3 4 5 6 7.

Chore

• Improve CI build times.
• Extract error messages from console logging in E2E tests.
• Reorganization of the E2E tests setup and expose it as npm packages.
• Add aXe accessibility E2E tests support.
• Add E2E tests for the excerpt meta box plugin.

Mobile

• Fix the Image Size implementation.
• Fix scrolling long text content.

#core-editor, #editor, #gutenberg