Skip to content

Update Block: Latest Comments #13931

Closed
Closed

Description

@melchoyce

Moved over from #1792.

Like Calendar and Archive, I looked at what a more dynamic Recent Comments block could include.

I focused on exploring the “what if’s” — what if you could approve pending comments in the Recent Comments block? What if you could reply to them?

image

View Prototype

Does this make sense? Should we try it out?

Activity

  1. karmatosed commented on Feb 18, 2019

    @karmatosed
    Member

    I love this idea. On one hand, it sits on the line whether it is an actual plugin/extending. On other, I love the idea that blocks become more dynamic.

  2. afercia commented on Feb 22, 2019

    @afercia
    Contributor

    Quickly discussed during today's accessibility bug-scrub and, besides the technical challenge (as far as I can tell this block is rendered server side, not sure it can be made dynamic) we have concerns about the overall proposal.

    In terms of interaction, we don’t think the post content is the place to manage comments.

    Also, with regards to approving comments, worth considering the widget-block by default displays only approved comments. That's its main purpose, as it's very unlikely authors want to display pending comments on the front end.

    Same applies to replying: not sure the post content is the right place for a complex interaction that should display an additional form with additional controls etc. That would be an unexpected interaction, especially for users with accessibility needs.

  3. added
    [Focus] Accessibility (a11y)Changes that impact accessibility and need corresponding review (e.g. markup changes).
    and removed on Feb 22, 2019
  4. mapk commented on Jun 4, 2019

    @mapk
    Contributor

    In the spirit of everything is a block, I really like this idea. I see it working in the context of block templates which is yet to come in the near future.

    Can we create a future label for this?

  5. added this to the Future milestone on Oct 10, 2019
  6. paaljoachim commented on Mar 10, 2020

    @paaljoachim
    Contributor

    A Latest Comments Block would be natural to include in a Query Block used in Full Site Editing.
    It would likely not be included in the content of a page or post.

  7. added
    [Priority] LowUsed to indicate that the issue at hand isn't a top priority to address and can be handled later
    on Apr 6, 2020
  8. paaljoachim commented on Aug 5, 2020

    @paaljoachim
    Contributor

    We discussed this during the Gutenberg Design Triage, and agreed that this would be a part of Full Site Editing.
    We need to circle around to this issue again sometime in the future.

  9. youknowriad commented on Aug 15, 2023

    @youknowriad
    Contributor

    I was checking old issues and came through this one now that we have FSE. Personally, I don't think like interacting with comments (managing them) in the editor is a good idea. Maybe in the frontend if you're an admin or things like that but I'm just tempted to just close this issue personally.

  10. karmatosed commented on May 7, 2025

    @karmatosed
    Member

    I also would say that interacting with comments in hindsight like this probably isn't the best approach with the direction site editing has gone. That in mind, I would recommend to close this out for now and consider if it ever is wanted to come back to it can be, closing doesn't mean we can't always iterate later. Thank you everyone for the work on this and perhaps some of the learnings can go to how collaborative editing is implemented even.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs DecisionNeeds a decision to be actionable or relevantNeeds DesignNeeds design efforts.[Block] Latest CommentsAffects the Latest Comments Block[Feature] Site EditorRelated to the overarching Site Editor (formerly "full site editing")[Focus] Accessibility (a11y)Changes that impact accessibility and need corresponding review (e.g. markup changes).[Priority] LowUsed to indicate that the issue at hand isn't a top priority to address and can be handled later

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      Sponsor
      SponsoredKunjungi sekarang
      Promo