Skip to content

Notes Sidebar container lacks independent mouse scrolling, freezing entirely when post content is short #80449

Description

@habiburdev

Description

Following on from the structural layouts introduced in Phase 3 of the Gutenberg roadmap, this issue serves as a critical bug report for the Notes UI container architecture planned for WordPress 7.1.

The current implementation of the right-hand Notes sidebar panel lacks an independent scroll property (such as overflow-y: auto). Instead, the scroll framework inherits and binds its viewport updates entirely to the height of the main post content canvas.

  • Long Content Layouts: If a post features a substantial body of text, scrolling the main editor canvas enables the sidebar to track vertically as an illusion of functional scrolling.
  • Short Content Layouts: If a post contains minimal text blocks while sustaining a high volume of notes or expanded reply threads, the sidebar panel completely freezes against mouse wheel and trackpad inputs.

Reproduction Profile

  1. Setup: Navigate to Posts -> Add New Post and generate a single short sentence block so the content height remains minimized.
  2. Context Creation: Highlight a section of the text, open the block toolbar options (⋮), and select Add note. Repeat this step to build multiple separate notes or long reply strings until the sidebar elements visually overflow past the bottom edge of the viewport.
  3. Execution: Position the mouse pointer directly within the boundary of the Notes sidebar panel and attempt a manual scroll gesture via mouse wheel or trackpad swipe.

Expected

The Notes sidebar panel should feature independent vertical viewport scrolling. Placing the cursor over the element and executing a scroll action must let the user freely browse through the active notes list, irrespective of the underlying post content canvas constraints.

Actual

The sidebar container remains completely static and locked against mouse/trackpad inputs due to the short post content blocking the window layout from triggering a scroll event. The current structural workaround requires clicking an upper visible note card to shift element focus, followed by using the keyboard's physical down arrow key to force the container to advance down.

Environment Details

  • WordPress Core: 7.1-beta1
  • Gutenberg Plugin: 23.5.3
  • Configuration: Clean install (All extraneous plugins deactivated)
  • Browsers Tested: Chrome (Latest)

Related / Cross-Reference:
Part of the WordPress 7.1 Notes testing cycle. This is distinct from deep reply box focus scrolling tracking in #73536; this bug targets a structural failure of global panel layout inheritance. Scoped for the tracking updates in #76316.

Step-by-step reproduction instructions

  1. Setup: Navigate to Posts -> Add New Post in the WordPress dashboard and type a single short sentence block so the main content canvas height remains minimized.
  2. Context Creation: Highlight a portion of the text, open the block toolbar options menu (⋮), and select Add note. Repeat this step to build multiple separate notes (or long reply strings) until the sidebar elements visually overflow past the bottom edge of the viewport.
  3. Execution: Position the mouse pointer directly within the boundary of the right-hand Notes sidebar panel and attempt a manual scroll gesture via a mouse wheel or trackpad swipe.

Screenshots, screen recording, code snippet

Image

Environment info

  • WordPress Core: 7.1-beta1
  • Gutenberg Plugin: 23.5.3
  • Configuration: Clean install (All extraneous plugins deactivated)
  • Browsers Tested: Chrome (Latest)
  • OS: macOS / Windows

Please confirm that you have searched existing issues in the repo.

  • Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

  • Yes

Please confirm which theme type you used for testing.

  • Block
  • Classic
  • Hybrid (e.g. classic with theme.json)
  • Not sure

Metadata

Metadata

Assignees

No one assigned

    Labels

    [Feature] NotesPhase 3 of the Gutenberg roadmap around block commenting[Type] BugAn existing feature does not function as intended

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions