Title: Help Test the Comments Blocks for WordPress 6.0
Author: JuanMa Garrido
Published: April 8, 2022
Last modified: December 19, 2023

---

 [  ](https://profiles.wordpress.org/juanmaguitar/) [JuanMa Garrido](https://profiles.wordpress.org/juanmaguitar/)
5:38 pm _on_ April 8, 2022     
Tags: [call for testing ( 27 )](https://make.wordpress.org/test/tag/call-for-testing/),
[gutenberg ( 75 )](https://make.wordpress.org/test/tag/gutenberg/)   

# Help Test the Comments Blocks for WordPress 6.0

The previously monolithic “Post Comments” 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. has been updated to work in a more flexible
and modular way by using child blocks. The new version is now called the “Comments
Query 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)”
block, and it comes with new blocks that can be used as child blocks within it. 
These new Comments blocks allow users to define and change the layout of the post
comments directly from the 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/)
editor.

## Table of Contents

 * [Help test this feature](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?output_format=md#Help-test-this-feature)
 * [How comments currently work in Full Site Editing](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?output_format=md#How-comments-currently-work-in-Full-Site-Editing)
 * [What’s new?](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?output_format=md#What%E2%80%99s-new?)
 * [Testing Environment ](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?output_format=md#Testing-Environment)
 * [Testing Instructions](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?output_format=md#Testing-Instructions)
 * [What to Test](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?output_format=md#What-to-test)

## Help test this feature

This post is a call for users to test the new blocks that can be used to build a
comments section in a page or post (following the block paradigm). The results of
this  testing will allow the contributors behind the development of these blocks
to decide whether or not they are ready to be included in the next release of WordPress(
v6.0) 

Please report your findings either as issues on 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/)
in the[ Gutenberg repository](http://github.com/wordpress/gutenberg) ,or in the 
comments below. If you have triage access, labelling any issue with “[Block] Comments
Query Loop” would be very helpful. Alternatively, you can start the title of your
issue with “Comments Blocks: ” to help those triaging the issues to label them appropriately.

## How comments currently work in Full Site Editing

The[ “Post Comments”](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/post-comments)
block is the block that currently manages a comments section on a post or page, 

> For example, the Twenty-Twenty-Two  theme uses this block in its “Single Post”
> template

![](https://lh5.googleusercontent.com/rW65Kzq4fmo8009YSxyMqcmALAX4xHYo461vSRjVeC4LtBzucwHerxfSF5zoyrbeuScCs0AKUgs1zyxG5Ti8_iKMaYkk3g-
4UE2LgoxJOXcdDgv_tY6Jjwzr8Jl3XZcR1u2GDkIu)

But with this “Post Comments” block no option exists** to change the styles and 
the layout of the comments from within the Editor. **This block uses the [comments_template()](https://developer.wordpress.org/reference/functions/comments_template/)
function internally to generate the HTMLHTML HTML is an acronym for Hyper Text Markup
Language. It is a markup language that is used in the development of web pages and
websites. for that section and the styles are defined via CSSCSS CSS is an acronym
for cascading style sheets. This is what controls the design or look and feel of
a site. files.

So, in summary, if you want to customize your comments section (change styles and
layout) when using this[ “Post Comments”](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/post-comments)
block you have to do a bit of coding

## What’s new?

With the new [Comments Query Loop](https://href.li/?https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comments-query-loop)
block, you now have available a set of child blocks that enable you to customize
the layout and styles of this section directly from within the Editor.

[[

The new Comments Blocks that are available from Gutenberg v13.0 are:

 * [Comments Query Loop](https://href.li/?https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comments-query-loop):
   An advanced block that  displays  post comments and allows for various layouts
   and  configurations.
    - [Comment Template](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comment-template):
      Contains the block elements used to display a comment, such as  the title,
      date, author, avatarAvatar An avatar is an image or illustration that specifically
      refers to a character that represents an online user. It’s usually a square
      box that appears next to the user’s name. and more.
       * [Avatar](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/avatar):
         Adds a user’s avatar.
       * [Comment Author Name](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comment-author-name):
         Displays the name of the author of the comment.
       * [Comment Date](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comment-date):
         Displays the date on which the comment was posted.
       * [Comment Content](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comment-content):
         Displays the contents of a comment.
       * [Comment Reply Link](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comment-reply-link):
         Displays a link to reply to a comment.
       * [Comment Edit Link](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comment-edit-link):
         Displays a link to edit the comment in the WordPress Dashboard. This link
         is only visible to users with the edit comment capability.
    - [Comments Pagination](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comments-pagination):
      Displays next/previous links to paginated comments where this has been enabled
      in the comment settings in the WordPress admin
       * [Previous Page](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comments-pagination-previous):
         Displays the link to the previous page of comments.
       * [Page Numbers](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comments-pagination-numbers):
         Displays a list of page numbers for comments pagination.
       * [Next Page](https://github.com/WordPress/gutenberg/tree/trunk/packages/block-library/src/comments-pagination-next):
         Displays the link to the next page of comments.

The addition of these blocks to Gutenberg is just the beginning. With these blocks,
in the future you will be able to create and share your own patterns for a comments
section.

## Testing Environment 

While there’s more information below to ensure you get everything set up properly,
here are the key things to consider with regard to your testing environment: 

 * Use a test site. Do not use a production/live site. You can[ follow these instructions](https://make.wordpress.org/core/handbook/tutorials/installing-wordpress-locally/)
   to set up a local installLocal Install A local install of WordPress is a way 
   to create a staging environment by installing a LAMP or LEMP stack on your local
   computer. or use a[ tool like this to set up a development site](https://localwp.com/).
 * Use WordPress 5.9.3 or the [latest version release page](https://github.com/WordPress/gutenberg/releases/latest)(
   downloadable[ here](https://wordpress.org/download/)).
 * Use the[ Twenty Twenty-Two theme](https://wordpress.org/themes/twentytwentytwo/).
   If you’d like to repeat the test or switch things up, you can always use a different
   [ block theme](https://wordpress.org/themes/tags/full-site-editing/).
 * Use [Gutenberg 13.0 RC](https://github.com/WordPress/gutenberg/releases/tag/v13.0.0-rc.2)
   or the latest version (download the `[gutenberg.zip](https://github.com/WordPress/gutenberg/releases/download/v13.0.0-rc.2/gutenberg.zip)`
   available from the release page). 

## Testing Instructions

**Set proper 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. and themes**

 1. Have a test site using the latest version of WordPress (5.9.3 at time of writing).
    It’s important that this is not a production/live site. 
 2. Install and activate the[ Twenty Twenty-Two theme](https://wordpress.org/themes/twentytwentytwo/)
    by going to _Appearances > Themes_. If you choose to use a different block theme,
    install and activate by going to _Appearances > Themes > Add New_ and searching
    for the one that has the _`Full Site Editing`_  listed as a feature. 
 3. Install and activate [Gutenberg 13.0 RC](https://github.com/WordPress/gutenberg/releases/tag/v13.0.0-rc.2)

**Customize the****_ “Single Post”_**** template to use the new ****_“Comments Query
Loop”_**** block**

 1. Go to the _“Single Post”_ template by:
 2.  a. Going to _Appearance > Editor_
     b. From the Template Editor click on the drop down menu in top centre  to choose 
        the template to Edit (_“Home”_ template selected by default)
     c. From that menú: _“Browse all templates”_ & select “Single Post”
 3. Remove the “Post Comments” block that you’ll find at the bottom with the text “
    Post comments block: no post found” 
 4. Insert in that same place the _“Comments Query Loop”_ block
 5. Save the _“Single Post”_ template with this new _“Comments Query Loop”_ block inserted

**Customize the Comments blocks styles and layouts and check the result of your 
changes in the frontend**

> _In order to ensure you have comments to play with you can _[_add demo content to your WordPress_](https://learn.wordpress.org/lesson-plan/how-to-add-demo-content-in-wordpress/)

 1. Go to the homepage of your testing site and go to the default _“Hello world!”_ 
    post to check how the Comments section looks by default with these new Comments
    blocks. You can also create a new post by going to _Posts > Add _
 2. Go to the_ “Single Post”_ template and [configure each comments block](https://wordpress.org/support/article/wordpress-editor/#configuring-a-block)
    to set the styles and layout you want
 3. Save the template and go to the post page to see your changes in the frontend (
    you’ll probably need to refresh the post’s page)
 4. Repeat this process as many times as you want and take note of any bug or User 
    Experience inconsistency you encounter during the process

**Insert the “Post Comments Form” block to check the behavior of the Comment Reply
Link and the ability to insert new comments**

> _The “Post Comments Form” cannot itself be customised via the Block Editor as 
> yet. _[_There’s an issue open to work on this_](https://github.com/WordPress/gutenberg/issues/38107)_
> but for the purpose of this testing we can just use it as it is and focus the 
> testing on the display of the comments_

 1. Go to the_ “Single Post”_ template and insert a “Post Comments Form” just after
    the “Comments Pagination” block
 2. Save the template and go to the post page to see if the form is available from 
    that page (you’ll probably need to refresh the post’s page)
 3. Submit a new comment and check whether the new comment appears and whether the 
    styles you defined for the Comments blocks are also applied to this new comment
 4. Check that the ”Comment Reply Link” and “Comment Edit Link” work properly 
 5. Take note of any bug or User Experience inconsistency you detect in the process

## What to test

So, what type of things can you test with these blocks?

This Call for Testing is mainly to check that these blocks work as expected, that
is, the changes in the styles and layout work as expected without bugs.

But just to provide some guidance, here are some aspects we specifically would like
to have some feedback about:

### Styles and Layout

Try to replicate a specific design on your comments section and check that you’re
able to implement that design using just  the Block Editor. For example you could
try to apply a Duotone 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. to the Avatar, or perhaps a two column layout with the avatar on the left
and rest of the content on the right – let your imagination run wild!

### 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)

Check that the comments section is fully accessible in both the Editor and the Frontend
and report any issues you find in this regard.

### Discussion Settings

Go to _Settings > Discussion_ and check that the different options are fully compatible
with the new Comments blocks (i.e. that they work as expected according to the options
that have been enabled/disabled).

![](https://lh5.googleusercontent.com/K5GZzUZpqtH4jFxJs4VBoiIhradkbtp25LQRhPqccGgS5uE-
mtd6SOK-ZEjIB1eNtGpdsfdXlUleU8un5XCD1U4rzy8Lx-ZemNYJkn5ZVR8UDVnbBdwbszAiCfaBaB-UlNhju-
lX)

### Pagination Links

Test that the pagination links work as expected. To test this you’ll need [enough comments for the comments to actually paginate](https://learn.wordpress.org/lesson-plan/how-to-add-demo-content-in-wordpress/).
Comment pagination also needs to be enabled in the WordPress admin under _Settings-
> Discussion -> Break comments into pages_

## **Thank you!**

Thank you for helping to test these new Comments Blocks! With the adoption of Full
Site Editing, bringing the power and flexibility of blocks to more parts of the 
page  is really helpful in enabling  users to customise their layouts and take full
control of their sites.

Thanks to [@mburridge](https://profiles.wordpress.org/mburridge/) [@cbravobernal](https://profiles.wordpress.org/cbravobernal/)
[@santosguillamot](https://profiles.wordpress.org/santosguillamot/) for reviewing
and helping shape this post

[#call-for-testing](https://make.wordpress.org/test/tag/call-for-testing/), [#gutenberg](https://make.wordpress.org/test/tag/gutenberg/)

### Share this:

 * [  Threads ](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?share=bluesky)
 * [  X ](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?share=x)
 * [  Facebook ](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?share=linkedin)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2022%2F04%2F08%2Fhelp-test-the-comments-blocks-for-wordpress-6-0%2F%23respond&locale=en_US)

### Like this:

Like Loading…

 1.  ![](https://secure.gravatar.com/avatar/0e8fe004d42b981872cb6fbc05963fa473d6a1917b514d0a415a1f04334093d0?
     s=32&d=identicon&r=g)
 2.   [JuanMa Garrido](https://profiles.wordpress.org/juanmaguitar/)  7:36 am _on_ 
     April 11, 2022
 3.  +make.wordpress.org/core/
 4.  ![](https://secure.gravatar.com/avatar/5829b86926e8946e34585c1937a39cb188ee38e8f34030d74d6404c972ea514e?
     s=32&d=identicon&r=g)
 5.   [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)  11:09 am
     _on_ April 11, 2022
 6.  I will add some comments as they come up while reading through the post above.
 7.  I will assume that the Comments Query 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)
     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 very similar in configuration as the Query Loop block. As they both use inner
     blocks to be able to better style post previews and comments based on how the 
     user wants it to look.
 8.  I do see one problem in relation to all the smaller inner blocks. As the Block
     Inserter can be filled up with blocks making it more difficult in finding the 
     blocks one needs. This means creating a better organized block library. There 
     is an issue for it somewhere on the 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/)
     repo that brings this up.
 9.  Next comment will be in relation to testing the Comments Query Loop.
 10.  * ![](https://secure.gravatar.com/avatar/5829b86926e8946e34585c1937a39cb188ee38e8f34030d74d6404c972ea514e?
        s=32&d=identicon&r=g)
      *  [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)  12:06
        pm _on_ April 11, 2022
      * Local test environment has been setup with WP 5.9.3.
         Twenty Twenty Two. 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/)
        13.0 RCRelease Candidate A beta version of software with the potential to be
        a final product, which is ready to release unless significant bugs emerge..
      * Switching out Post comment 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. with Comments Query 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)
        block. There should be a **transform to** making it possible to switch between
        the two using transform.
         I manually deleted and added the Comments Query Loop
        block. [https://github.com/WordPress/gutenberg/issues/40223](https://github.com/WordPress/gutenberg/issues/40223)
      * Post Comments is within a Group within another Group within another Group. 
        Here it would be helpful to rename the blocks in List view. [https://github.com/WordPress/gutenberg/issues/33583#issuecomment-1094934784](https://github.com/WordPress/gutenberg/issues/33583#issuecomment-1094934784)
      * Sometimes the contextual drop down menu will go below the edge of the browser
        not making it possible to delete a block. One has to wiggle around for the 
        drop down to show up above the toolbar or that a scrollbar will be added. [https://github.com/WordPress/gutenberg/issues/40224](https://github.com/WordPress/gutenberg/issues/40224)
      * Switch between the old and new Comments blocks.
         Opened the test site in a 
        private tab (not logged in tab). Hmm the new block is not showing a comments
        area on the frontend as the old block did. [https://github.com/WordPress/gutenberg/issues/40225](https://github.com/WordPress/gutenberg/issues/40225)
        I will need to experiment and see if I can figure out what is going on.
      * Posting this comment. Will continue when I am able to do so.
      * ![](https://secure.gravatar.com/avatar/0e8fe004d42b981872cb6fbc05963fa473d6a1917b514d0a415a1f04334093d0?
        s=32&d=identicon&r=g)
      *  [JuanMa Garrido](https://profiles.wordpress.org/juanmaguitar/)  5:07 pm _on_
        April 11, 2022
      * [@paaljoachim](https://profiles.wordpress.org/paaljoachim/) Thanks a lot for
        your feedback!
         Let me answer to each of your comments
      * 
        #### 󠀁[On the organization of blocks and finding the ones needed](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?output_format=md#comment-2407)󠁿
        
      * > I do see one problem in relation to all the smaller inner blocks. As the 
        > 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. Inserter can be filled up with blocks making it 
        > more difficult in finding the blocks one needs. This means creating a better
        > organized block library.
      * Although not directly related with the Comments blocks, this is a valid issue,
        but one that requires some input from a designer to resolve it.
      * I’ve created this issue to have a proper conversation about this: [https://github.com/WordPress/gutenberg/issues/40233](https://github.com/WordPress/gutenberg/issues/40233)
      * Feel free to add more feedback about this feature in the 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/) Issue.
      * 
        #### 󠀁[On the switch from Post Comment block to Comments Query Loop
        
      * > Switch between the old and new Comments blocks.
        >  Opened the test site in 
        > a private tab (not logged in tab). Hmm the new block is not showing a comments
        > area on the frontend as the old block did.
      * The conversation has continued in the issue [https://github.com/WordPress/gutenberg/issues/40225](https://github.com/WordPress/gutenberg/issues/40225)
        and there are some new responses there
      * 
        #### 󠀁[On a transform between Post Comments and Comments Query Loop blocks](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?output_format=md#comment-2408)󠁿
        
      * > Switching out Post comment block with Comments Query 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)
        > block. There should be a transform to making it possible to switch between
        > the two using transform.
        >  I manually deleted and added the Comments Query
        > Loop block.
      * The conversation has continued in the issue [https://github.com/WordPress/gutenberg/issues/40223](https://github.com/WordPress/gutenberg/issues/40223)
        and there are some new responses there
      * 
        #### 󠀁[On renaming the Group blocks related to Comments in the List view](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?output_format=md#comment-2408)󠁿
        
      * > Post Comments is within a Group within another Group within another Group.
        > Here it would be helpful to rename the blocks in List view.
      * Although not directly related with the Comments blocks, this is an interesting
        issue, thanks for highlighting it.
      * The conversation has continued in the issue [https://github.com/WordPress/gutenberg/issues/33583#issuecomment-1094934784](https://github.com/WordPress/gutenberg/issues/33583#issuecomment-1094934784)
        from your comment and there are some new responses there
      * 
        #### 󠀁[On the contextual drop down not displaying all the options](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?output_format=md#comment-2408)󠁿
        
      * > Sometimes the contextual drop down menu will go below the edge of the browser
        > not making it possible to delete a block. One has to wiggle around for the
        > drop down to show up above the toolbar or that a scrollbar will be added
      * This is unrelated to the Comments blocks. but It’s a legit problem though. 
        The issue [https://github.com/WordPress/gutenberg/issues/40224](https://github.com/WordPress/gutenberg/issues/40224)
        has been added to the WP 6.0 milestone.
         - ![](https://secure.gravatar.com/avatar/5706550a5b705b844cfcacac6f96493d9184c0fe21b44d260df307e8de667a4e?
           s=32&d=identicon&r=g)
         -  [Jonas](https://profiles.wordpress.org/elbsegler/)  6:53 am _on_ April 
           12, 2022
         - [@juanMa](https://profiles.wordpress.org/juanma/)
            Thank you for this detailed
           answer.
         - ![](https://secure.gravatar.com/avatar/5829b86926e8946e34585c1937a39cb188ee38e8f34030d74d6404c972ea514e?
           s=32&d=identicon&r=g)
         -  [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)  8:
           10 am _on_ April 12, 2022
         - My testing continues.
            I found out that the Post Comments 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 replaced by the Comments Query 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)
           block AND the Post Comments Form block. It should become the new default
           when opening the Single Post template.
         - Experimenting with 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. options.
            What about adding a
           border, radius and padding to the Comments Query Loop? See this issue: [https://github.com/WordPress/gutenberg/issues/40247](https://github.com/WordPress/gutenberg/issues/40247)
         - I noticed when adding long text that was initially written as paragraphs
           that the text was lumped into one text.
            I made this issue: [https://github.com/WordPress/gutenberg/issues/40248](https://github.com/WordPress/gutenberg/issues/40248)
         - What about making it possible to have initial comment one color and the 
           reply to a comment another color?
         - Pagination works fine.
            1- What about renaming Older Comments and Newer 
           Comments? As if these were regular text. As one might want to call these
           something else then the default text used.
         - 2- Btw I see that one can change the background color of Older Comments/
           Newer Comments but not Page Numbers. What about changing the text color 
           of all of these?
         - 3- Today going to the parent Comments Pagination and changing the color 
           will only affect the Page Numbers. This seems kind of weird. I would think
           that changing the Comments Pagination text color would affect all there 
           areas. (Older Comments, Newer Comments and Page Numbers.)
         - 4- Clicking Newer Comments/Older Comments or a number the page will jump
           to the top, and I have to scroll back down to the comments. I would expect
           it to jump to the first comment and not the top of the page.
         - 5- Making it possible to have Page Numbers on the left and Older/Newer Comments
           text on the right (two different alignments in the same row). I do not know
           how we would do so at present time. Actually “Change Items Justification”
           works that way. Clicking “Space between items” Page Numbers are seen on 
           the left, Newer Comments are seen in the middle and Older Comments are seen
           on the right atleast in the backend. The Frontend shows Older/Newer Comments
           on the right side and Page Numbers on the left. Meaning there is some visual
           discrepancy backend frontend. (Not sure if we should do anything about that.)
         - Comment Date.
            Changing the Comment Date text. As we might want to use some
           other text.
         - Comment Content.
            Add a border radius and border.
         - Comment Author
            Aligning middle or right has no effect on the frontend. 
           Changing text color has no effect on the frontend. I made this issue: [https://github.com/WordPress/gutenberg/issues/40251](https://github.com/WordPress/gutenberg/issues/40251)
         - Comment Template -> Columns.
            Changing background to a darker color and 
           changing the text to white changes: Comment Date, Comment Author and Comment
           Content, but not Edit and Reply. Issue: [https://github.com/WordPress/gutenberg/issues/40255](https://github.com/WordPress/gutenberg/issues/40255)
         - Changing parent column text color and then inner child block text color.
           Which should show the text color?
            [https://github.com/WordPress/gutenberg/issues/40257](https://github.com/WordPress/gutenberg/issues/40257)
         - Posting this information, and will likely continue testing later on.
            * ![](https://secure.gravatar.com/avatar/5829b86926e8946e34585c1937a39cb188ee38e8f34030d74d6404c972ea514e?
              s=32&d=identicon&r=g)
            *  [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)  
              11:48 am _on_ April 12, 2022
            * Additional testing.
               Comments Query 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)
              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.. Testing alignments seeing
              no difference. Issue: [https://github.com/WordPress/gutenberg/issues/40269](https://github.com/WordPress/gutenberg/issues/40269)
            * Testing alignments with the author block.
               Right Alignment is not working
              correctly. Issue: [https://github.com/WordPress/gutenberg/issues/40271](https://github.com/WordPress/gutenberg/issues/40271)
            * Changing the vertical alignment inside Comments Query Loop > Comment 
              Template > Columns > Row. Affects the Comment Edit Link and not the Comment
              Date. Issue: [https://github.com/WordPress/gutenberg/issues/40272](https://github.com/WordPress/gutenberg/issues/40272)
            * Regarding Comment Edit Link. The block also has text alignments which
              looks like it is not working. (No issue yet.)
            * Comment Author Name and Comment Reply Link alignment is also not working.(
              No issue yet.) Backend shows correctly but frontend does not.
            * I will stop the testing there, as the various things I mentioned is more
              then enough to fix in this round. PingPing The act of sending a very 
              small amount of data to an end point. Ping is used in computer science
              to illicit a response from a target server to test it’s connection. Ping
              is also a term used by Slack users to @ someone or send them a direct
              message (DM). Users might say something along the lines of “Ping me when
              the meeting starts.” me on 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/)
              for testing PR’s and in general for additional testing.
 11. ![](https://secure.gravatar.com/avatar/62ddf5ea97513ec704f8cf2b3c2afe218655b2b9e64c9237c7b99feb343a39eb?
     s=32&d=identicon&r=g)
 12.  [Ugyen Dorji](https://profiles.wordpress.org/ugyensupport/)  7:37 am _on_ April
     12, 2022
 13. [@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/)
      Does that mean 
     Post-Comment 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. would support only to it’s respective Blog Post?
 14. ![](https://secure.gravatar.com/avatar/8013a62d7397c006bae48b96d6832a573ea71a7d5d3597fe584210567b508c05?
     s=32&d=identicon&r=g)
 15.  [Justin Tadlock](https://profiles.wordpress.org/greenshady/)  6:42 am _on_ April
     13, 2022
 16. I wrote about issues more extensively [in a blog post](https://wptavern.com/new-comment-related-blocks-arriving-with-wordpress-6-0),
     but the following are what I would consider blockers:
 17.  a. Missing `#comment-id` on the comment wrapper element.
      b. Missing output of `comment_class()` on wrapper element (see post query implementation).
      c. No comments title 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. (e.g., “X responses to post title”).
 18.  * ![](https://secure.gravatar.com/avatar/383e4c3de69b7573457fddff91cf5c33f1241892041cebdeeea4a4b38c04debd?
        s=32&d=identicon&r=g)
      *  [Michael Burridge](https://profiles.wordpress.org/mburridge/)  3:29 pm _on_
        April 13, 2022
      * The response to the call for testing of the Comments Query 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)
        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. has been fantastic and the work of everyone involved in testing
        is much appreciated.
      * The call for testing has resulted in [a number of issues](https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is%3Aissue+label%3A%22%5BBlock%5D+Comments+Query+Loop%22)
        being raised since the call which will help contributors to continue work on
        the Comments Query Loop block in order to ultimately achieve feature parity
        with the current Post Comments block (which as you noted in [the article](https://wptavern.com/new-comment-related-blocks-arriving-with-wordpress-6-0)
        is simply a wrapper for the PHPPHP PHP (recursive acronym for PHP: Hypertext
        Preprocessor) is a widely-used open source general-purpose scripting language
        that is especially suited for web development and can be embedded into HTML.
        [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php)
        rendered comments query).
      * Thank you for the testing you’ve conducted and reported on in your article.
        You’ve raised a number of important issues:
      * _1 “Missing `#comment-id` on the comment wrapper element.”_
      * There’s [a currently open PR](https://github.com/WordPress/gutenberg/pull/40268)
        that attempts to address this issue, though it appears that this isn’t as easy
        to address as might at first seem.
      * _2 “Missing output of `comment\_class()` on wrapper element (see post query
        implementation).”_
      * Thanks for highlighting this, JuanMa has created [this issue](https://github.com/WordPress/gutenberg/issues/40306)
        directly in response to your point.
      * _3 “No comments title block (e.g., “X responses to post title”).”_
      * [This issue](https://github.com/WordPress/gutenberg/issues/40264) has been 
        created in response to the call for testing which specifically addresses this.
      * In addition to the points you raised a number of conversations around the Comments
        Query Loop block are currently underway.
      * One conversation taking place is whether or not to include the Comments Query
        Loop block in a WordPress release before feature parity with the Post Comments
        block is achieved.
      * Another conversation is, if so – _i.e._ if the Comments Query Loop block is
        included before feature parity – then should we continue to include the existing
        Post Comments block in WordPress until the Comments Query Loop block achieves
        feature parity, taking into account that it could be confusing for users to
        have two blocks that provide similar functionality.
      * Work on the Comments Query Loop block will be ongoing for quite a while, certainly
        beyond the release of WP 6.0.
      * There is [this tracking issue](https://github.com/WordPress/gutenberg/issues/34994)
        for anyone interested to keep up to date with progress on the Comments Query
        Loop block.
         - ![](https://secure.gravatar.com/avatar/8013a62d7397c006bae48b96d6832a573ea71a7d5d3597fe584210567b508c05?
           s=32&d=identicon&r=g)
         -  [Justin Tadlock](https://profiles.wordpress.org/greenshady/)  3:59 pm _on_
           April 13, 2022
         - Thanks for linking up those tickets, Michael.
         - >  One conversation taking place is whether or not to include the Comments
           > Query 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)
           > 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. in a WordPress release before
           > feature parity with the Post Comments block is achieved.
         - I believe that that we can at least have it an as option for theme authors
           to use. I said the other things were blockers, and maybe they are. However,
           the most important thing would be the Comment ID. That directly affects 
           the functionality of commenting and breaks comment permalinks. If this is
           added, themes could at least effectively use Comments Query Loop, even if
           they have to hack something like the “comments title/heading” together.
            * ![](https://secure.gravatar.com/avatar/383e4c3de69b7573457fddff91cf5c33f1241892041cebdeeea4a4b38c04debd?
              s=32&d=identicon&r=g)
            *  [Michael Burridge](https://profiles.wordpress.org/mburridge/)  4:15 
              pm _on_ April 13, 2022
            * > the most important thing would be the Comment ID
            * Fortunately, since you say this is the most important thing, it is the
              one that is [being focused on](https://github.com/WordPress/gutenberg/pull/40268)
              as it’s recognised that this is fairly critical.
            * However, be assured that your other points will also be addressed.

### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/test/2022/04/08/help-test-the-comments-blocks-for-wordpress-6-0/?output_format=md#respond)󠁿

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2022%2F04%2F08%2Fhelp-test-the-comments-blocks-for-wordpress-6-0%2F&locale=en_US)
to post a comment.

# Post navigation

[← FSE Program Hyping Headers Summary](https://make.wordpress.org/test/2022/04/05/fse-program-hyping-headers-summary/)

[Help Wanted: Test WordPress 6.0 →](https://make.wordpress.org/test/2022/04/12/help-wanted-test-wordpress-6-0/)