Skip to content

Support Notes on content spanning multiple blocks #73416

Description

@jeffpaul

What problem does this address?

Currently, Notes can only be attached to a single block. This limitation becomes restrictive in cases where feedback applies to text or content that spans multiple blocks, such as a paragraph flowing into another paragraph, a heading with a follow-up block, or multi-block sections that represent a single idea. Supporting Notes across multiple blocks would allow reviewers to leave feedback that more accurately reflects the structure and intent of the content instead of forcing them to choose one arbitrary block as the anchor.

Note that Notes within the content of a single block is being tracked in #59445.

What is your proposed solution?

The feature should allow a Note to reference a range of content that begins in one block and extends into one or more subsequent blocks. This may require a way to define a selection range that is not block-bounded, along with UI that shows a clear visual anchor for where the Note applies. The Note should remain stable across edits, even if blocks are split, merged, or moved. Both the floating Notes view and the sidebar panel (archive view) should be able to display and navigate to multi-block anchored Notes consistently. The technical approach will need to consider how ranges are stored, how to handle partially deleted content, and how to maintain accessibility and clarity for users navigating via keyboard or screen readers.

Open questions:

  1. How should multi-block ranges be selected in the editor?
  2. What is the best model for storing cross-block ranges (per-block offsets, selection ranges, etc.)?
  3. How should Notes behave when blocks are merged, split, or rearranged?
  4. How should the floating UI indicate that a Note applies to more than one block?
  5. Should this support only adjacent blocks, or any arbitrary set of blocks (e.g. multiple image blocks requesting duotone edits)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs DesignNeeds design efforts.[Feature] NotesPhase 3 of the Gutenberg roadmap around block commenting[Type] EnhancementA suggestion for improvement.
    No fields configured for Enhancement.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions