Title: What’s new in Gutenberg? (26th June) Author: Riad Benguella Published: June 26, 2019 Last modified: May 20, 2020 --- [ ](https://profiles.wordpress.org/youknowriad/) [Riad Benguella](https://profiles.wordpress.org/youknowriad/) 12:50 pm _on_ June 26, 2019 Tags: [core-editor ( 761 )](https://make.wordpress.org/core/tag/core-editor/), [editor ( 223 )](https://make.wordpress.org/core/tag/editor/), [gutenberg ( 553 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-new ( 220 )](https://make.wordpress.org/core/tag/gutenberg-new/)    # What’s new in Gutenberg? (26th June) Last week saw WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). Europe bring many contributors to Berlin, an event which brings us together across focuses and even languages. Still, we’re back to business as usual and 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/) 6.0 is a release packed with 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 and improvements. The Widgets screen is being polished, the Group 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. is being improved and 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) remains an important focus. This release also features a layout picker for the Columns block, allowing the user to choose from pre-defined layouts or to start from scratch. ## 6.0 ### Features * Support choosing a [pre-defined layout for the Columns block](https://github.com/WordPress/gutenberg/pull/16129). The user can choose between multiple column and width arrangements. ### Enhancements * Add [Snackbar notices](https://github.com/WordPress/gutenberg/pull/16020) support to the widgets screen. * Add an [inner container to the Group](https://github.com/WordPress/gutenberg/pull/15210) [block](https://github.com/WordPress/gutenberg/pull/16202) to simplify theme styling. * Avoid stacking successive [MediaPlaceholder errors](https://github.com/WordPress/gutenberg/pull/14721). * Adjust the [DatePicker margins](https://github.com/WordPress/gutenberg/pull/16097). * Update the [Tag Cloud block](https://github.com/WordPress/gutenberg/pull/16098) [copy](https://github.com/WordPress/gutenberg/pull/16107) when no terms are found. * Add descriptive text and a link to [documentation in embed blocks](https://github.com/WordPress/gutenberg/pull/16101). * Improve placeholder text [phrasing for media blocks](https://github.com/WordPress/gutenberg/pull/16135). * Use classnames for the [text alignments in the heading block](https://github.com/WordPress/gutenberg/pull/16035). * Make the [inserter category icons grayscale](https://github.com/WordPress/gutenberg/pull/16163). * 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): Make the [modal overlay scrim darker](https://github.com/WordPress/gutenberg/pull/15974). ### Bug Fixes * Fix [warning messages triggered by the Group block](https://github.com/WordPress/gutenberg/pull/16096) icons. * Fix [horizontal scrollbar on full-wide blocks](https://github.com/WordPress/gutenberg/pull/16085) with nesting. * A11y:  - Re-enable the [menu item hover state](https://github.com/WordPress/gutenberg/pull/16168) on small screens. - Correct text zoom issue in the [Content Structure popover](https://github.com/WordPress/gutenberg/pull/15984). * Fix the [Popovers position](https://github.com/WordPress/gutenberg/pull/15949) in the widgets screen. * Fix the behavior of the [block toolbars in the widgets screen](https://github.com/WordPress/gutenberg/pull/15470). * Fix the editor in IE11 (use the [CJS version of react-spring](https://github.com/WordPress/gutenberg/pull/16196)). * Fix formatting of the [validation error messages](https://github.com/WordPress/gutenberg/pull/16173) in the console. * Fix breakage when the [CPT doesn’t support title](https://github.com/WordPress/gutenberg/pull/16236). ### Various * Document and simplify the [multi-entrypoints support](https://github.com/WordPress/gutenberg/pull/15982) in the wordpress/scripts package.  * Create sub-registry automatically when using [EditorProvider](https://github.com/WordPress/gutenberg/pull/15989). * Use classnames utility instead of concatenating [classnames in the TabPanel](https://github.com/WordPress/gutenberg/pull/16081) component. * Remove the default value for the [required onRequestClose prop](https://github.com/WordPress/gutenberg/pull/16074) in the Modal component. * Remove the [editor package dependency](https://github.com/WordPress/gutenberg/pull/15548) from the media blocks. * Fix the [playground build](https://github.com/WordPress/gutenberg/pull/15947) script. * Fix the [Github action assigning milestones](https://github.com/WordPress/gutenberg/pull/16084). * Fix [naming conventions](https://github.com/WordPress/gutenberg/pull/16091) for function containing CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. keyword. * Fix the [Travis build artifacts job](http://update/build-artifacts-npm-install) to use a full npm install while building. * Make [Calendar block resilient](https://github.com/WordPress/gutenberg/pull/16161) to the editor module not being present. * Ensure the Snackbar component is only used with a [single action button](https://github.com/WordPress/gutenberg/pull/16095). * Remove [SlotFillProvider and DropZoneProvider](https://github.com/WordPress/gutenberg/pull/15988) from the BlockEditorProvider. * Add the initial version of the [Block Registration RFC](https://github.com/WordPress/gutenberg/pull/13693). * Add [popoverProps prop to the Dropdown](https://github.com/WordPress/gutenberg/pull/14867) component. * Update [Image Block’s image classes](https://github.com/WordPress/gutenberg/pull/15464) with dimensions. * Support registering [custom grouping blocks](https://github.com/WordPress/gutenberg/pull/15774). * Fix h1 heading typo so [h1 is same size as title](https://github.com/WordPress/gutenberg/pull/16253). * Remove the [custom class support from the legacy widget](https://github.com/WordPress/gutenberg/pull/16231) block. ### Documentation * Prefer [register_post_meta](https://github.com/WordPress/gutenberg/pull/16032) over register_meta. * Add [mention of Figma](https://github.com/WordPress/gutenberg/pull/16140) to the design contributing docs. * Add [supported attribute types](https://github.com/WordPress/gutenberg/pull/16220) for the Blocks 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.. * Enhance the [Annotations API](https://github.com/WordPress/gutenberg/pull/16233) documentation. * Tweaks and typos: [1](https://github.com/WordPress/gutenberg/pull/16083), [2](https://github.com/WordPress/gutenberg/pull/16073), [3](https://github.com/WordPress/gutenberg/pull/16087), [4](https://github.com/WordPress/gutenberg/pull/16102), [5](https://github.com/WordPress/gutenberg/pull/16145), [6](https://github.com/WordPress/gutenberg/pull/16143), [7](https://github.com/WordPress/gutenberg/pull/16144), [8](https://github.com/WordPress/gutenberg/pull/16232), [9](https://github.com/WordPress/gutenberg/pull/16121), [10](https://github.com/WordPress/gutenberg/pull/16235), [11](https://github.com/WordPress/gutenberg/pull/15394). ### Mobile * Fix [multiline Image block captions](https://github.com/WordPress/gutenberg/pull/16071) in iOSiOS The operating system used on iPhones and iPads.. * Avoid unnecessary [div elements in the content of Quote](https://github.com/WordPress/gutenberg/pull/16072) blocks. * Update the default [colors used in the RichText](https://github.com/WordPress/gutenberg/pull/16016) component. * Fix [pasting text on Post Title](https://github.com/WordPress/gutenberg/pull/16116). * Unify the web and mobile components hierarchy: - [BlockPicker and Inserter](https://github.com/WordPress/gutenberg/pull/16114). - [BlockToolbar](https://github.com/WordPress/gutenberg/pull/16213). - [BlockMobileToolbar](https://github.com/WordPress/gutenberg/pull/16177). - [BlockListBlock](https://github.com/WordPress/gutenberg/pull/16223). - [BlockList](https://github.com/WordPress/gutenberg/pull/16239). * Add native component [HTMLTextInput](https://github.com/WordPress/gutenberg/pull/16226). * Update the video player to [open the URL by browser](https://github.com/WordPress/gutenberg/pull/16089) on Android. * Re-enable the [Video block on Android](https://github.com/WordPress/gutenberg/pull/16215). ## Performance Benchmark The following benchmark compares performance for a particularly sizeable post (~ 36000 words, ~ 1000 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 6.0.0 | 5.1s | 80.39ms | | Gutenberg 5.9.0 | 4.8s | 69ms | | Gutenberg 5.3 (WordPress 5.2) | 7.1s | 77ms | --- 👏 Kudos to all the contributors. Thank you. [#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/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2019/06/26/whats-new-in-gutenberg-26th-june/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2019/06/26/whats-new-in-gutenberg-26th-june/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2019/06/26/whats-new-in-gutenberg-26th-june/?share=bluesky) * [ X ](https://make.wordpress.org/core/2019/06/26/whats-new-in-gutenberg-26th-june/?share=x) * [ Facebook ](https://make.wordpress.org/core/2019/06/26/whats-new-in-gutenberg-26th-june/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2019/06/26/whats-new-in-gutenberg-26th-june/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/250257111d1248c34046552bbcdf6999949ef56b2f992dd5eb39bf45cabeb18a? s=32&d=mm&r=g) 2. [Samuel Wood (Otto)](https://profiles.wordpress.org/otto42/) 12:55 pm _on_ June 26, 2019 3. Can we please define terms so that people know what is being discussed? What the heck is a “snackbar”? 4. * ![](https://secure.gravatar.com/avatar/82e9a51f6e6724d0f49489c10f8ef90d6b15434208f92d35d46ce7c2c09fa132? s=32&d=mm&r=g) * [Felipe Elia](https://profiles.wordpress.org/felipeelia/) 1:11 pm _on_ June 26, 2019 * Coming from an Android development background, I knew these as “Toasts”. Anyway, it is this type of notice: * ![](https://i2.wp.com/wptavern.com/wp-content/uploads/2019/06/snackbars.gif? ssl=1) - ![](https://secure.gravatar.com/avatar/f2ec9d515c7c2ee558e338e5daa1e42c2cbe2cd6935ab08c8e6b9a71cf5f3f99? s=32&d=mm&r=g) - Anonymous User 2:56 am _on_ June 27, 2019 - When will merge this feature with WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.? * ![](https://secure.gravatar.com/avatar/fa9bb9feab2f2f97662e7b07c9deaf0aca3ec7c037840a8cc3563ec022f77048? s=32&d=mm&r=g) * [Miguel Fonseca](https://profiles.wordpress.org/mcsf/) 9:30 am _on_ July 2, 2019 * 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/) 6.0 will make its way into WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. in the next major version, WP 5.3. There is no release schedule for 5.3 yet, but you can monitor the [5.3 Development Cycle](https://make.wordpress.org/core/5-3/) page. * Meanwhile, you can use Gutenberg as a regular WordPress 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., giving you all the latest features ahead of time. 5. ![](https://secure.gravatar.com/avatar/4f0eccb031d85379ec66f7afef961faf7fcf3553629d217f7b082ee2daf9752f? s=32&d=mm&r=g) 6. [dsaull](https://profiles.wordpress.org/dsaull/) 3:44 am _on_ June 30, 2019 7. When will the 6.0 be integrated into WP? I want to use the new Column features for photos.. 8. * ![](https://secure.gravatar.com/avatar/fa9bb9feab2f2f97662e7b07c9deaf0aca3ec7c037840a8cc3563ec022f77048? s=32&d=mm&r=g) * [Miguel Fonseca](https://profiles.wordpress.org/mcsf/) 9:30 am _on_ July 2, 2019 * 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/) 6.0 will make its way into WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. in the next major version, WP 5.3. There is no release schedule for 5.3 yet, but you can monitor the [5.3 Development Cycle](https://make.wordpress.org/core/5-3/) page. * Meanwhile, you can use Gutenberg as a regular WordPress 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., giving you all the latest features ahead of time. Comments are closed. # Post navigation [← Editor Chat Agenda: June 26th](https://make.wordpress.org/core/2019/06/26/editor-chat-agenda-june-26th/) [Editor chat summary: 26 June 2019 →](https://make.wordpress.org/core/2019/06/26/editor-chat-summary-26-june-2019/)