Skip to content

Notes: mention notification link opens the post but the Notes panel is hidden behind the default editor sidebar #82102

Description

@jordesign

Description

When a user clicks a deep-link from a Note mention notification email, the correct post opens in the editor and the referenced note is deep-linked in the Notes panel — but the default editor sidebar (document/block settings) is active on page load, visually covering the Notes panel.

From the user's perspective the notification link "opens the post but not the note", because the Notes panel is not visible without manually switching sidebars. The behaviour is correct underneath — the note is focused — it's just obscured by the default sidebar state on entry.

Screen.Recording.2026-08-27.at.13.20.28.mov

Steps to reproduce

  1. User A mentions user B in a note on a post.
  2. User B opens the notification email and clicks the link.
  3. Editor opens on the correct post.
  4. Observe the sidebar: the default document/block settings sidebar is showing, not the Notes panel.

Expected

When the editor opens via a note-deep-link, the Notes panel is the active sidebar (or otherwise visible) so the referenced note is on-screen immediately.

Actual

The default sidebar covers the Notes panel. The user has to manually open the Notes panel to see the note they were sent to.

Reporter's own words

The link in the Note notification email opens the correct post in the editor, but it does not open the Notes sidebar or focus the specific Note referenced in the notification. I'd expect the link to take the recipient directly to the relevant Note.

Activity

  1. changed the title [-]Notes: opening a deep-link from a mention notification opens the post but the Notes panel is hidden behind the default editor sidebar[/-] [+]Notes: mention notification link opens the post but the Notes panel is hidden behind the default editor sidebar[/+] on Aug 27, 2026
  2. himanshupathak95 commented on Aug 28, 2026

    @himanshupathak95
    Contributor

    Thanks for filing this.

    Small correction to the framing: it's not that the note is hidden behind the sidebar, I think it's more like the notification email doesn't reference the specific note at all. It just links via get_edit_post_link(), with no query param or client-side handling to identify or focus a note on load. So right now, clicking the link just opens the post with whatever sidebar tab was last open.

    Simplest solution for this coming in my mind is to add the comment ID to the notification link as a query arg (?note=123).
    Then we can read it once on mount, same pattern BrowserURL uses for ?revision= (useState(() => getQueryArg(...)))
    Pass it into the existing focusNote() call in the Notes sidebar which already knows how to pick the right sidebar and spotlight the block, just isn't called on initial load.

    Thoughts on this?

  3. himanshupathak95 commented on Aug 28, 2026

    @himanshupathak95
    Contributor

    This is how it looks in my testing -

    Screen.Recording.2026-08-28.at.09.1.mp4

    Found a related edge case while testing the fix: the note-to-block link is only a local editor edit and it's not persisted until the post itself is saved, even though the note comment is saved immediately. So if someone adds a note, mentions someone, and doesn't save/publish the post afterward, the recipient's link will still land on the default sidebar, because there's no saved block to focus yet.
    But if we manually open and check the notes sidebar panel, we will still be able to see the note but with the title "Original Block deleted." -

    Image

    This isn't something to fix here itself (it would mean auto-saving the post whenever a note is added, which is a separate decision atlogether) Just mentioning here or maybe a seperate issue can be opened for this for discussion.

  4. Mamaduka commented on Oct 15, 2026

    @Mamaduka
    Member

    So if someone adds a note, mentions someone, and doesn't save/publish the post afterward, the recipient's link will still land on the default sidebar, because there's no saved block to focus yet.

    This is tracked here: #72717

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

    [Feature] NotesPhase 3 of the Gutenberg roadmap around block commenting

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions