[Beta]: Accepting the seeded removal suggestion crashes the homepage Playground

[felixfeng33]

Bug type

Crash (process/app exits or hangs)

Browser surface

Yes

Summary

Accepting the seeded mark text for removal suggestion in the Plate next/Beta homepage Playground crashes the page with a DOM removeChild NotFoundError.

Public reproduction URL

NOT_ENOUGH_INFO

Steps to reproduce

1. Open the Plate next/Beta homepage.
2. In the Playground's Collaborative Editing section, click the red mark text for removal suggestion.
3. In the Delete: mark text for removal card, click the checkmark to accept the suggestion.
4. Observe that the Playground is replaced by a runtime error overlay.

Expected behavior

The accepted removal suggestion should delete mark text for removal, close its suggestion card, and leave the Playground usable. Authority: the current editor.update.suggestion.accept package test verifies that accepting a remove suggestion removes the marked text, and the homepage card's checkmark calls that API.

Actual behavior

The page immediately switches to a Next.js runtime error overlay:

Runtime NotFoundError
Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

The visible call stack begins at button / <anonymous>.

Acceptance criteria

• Accepting the seeded mark text for removal suggestion removes the marked text.
• The suggestion card closes without a runtime error.
• The homepage Playground remains interactive after acceptance.
• Browser regression coverage exercises this exact homepage suggestion-accept path and asserts that no page error occurs.

Plate / Slate / React versions

plate: NOT_ENOUGH_INFO
plite: NOT_ENOUGH_INFO
suggestion: NOT_ENOUGH_INFO
react: NOT_ENOUGH_INFO
next: 16.2.6

Operating system

NOT_ENOUGH_INFO

Install method

NOT_ENOUGH_INFO

Framework / app setup

Next.js 16.2.6 homepage Playground

Affected packages or entry points

Plate next/Beta homepage Playground; apps/www homepage suggestion-card integration; @platejs/suggestion acceptance path. The recording does not establish the root-owning package.

Minimal code or config excerpt

const accept = (suggestion: ResolvedSuggestion) => {
  editor.update.suggestion.accept(suggestion);
};

<Button onClick={() => accept(suggestion)}>
  <CheckIcon />
</Button>

Logs, screenshots, and evidence

Supplied GIF: 5.04 seconds, 800x531.
~0:01: clicking `mark text for removal` opens the deletion-suggestion card.
~0:02.6: clicking the card's checkmark accepts the suggestion.
~0:03.2: the page is replaced by the `removeChild` `NotFoundError` overlay.

Impact and severity

Affected: users testing suggestion acceptance in the Plate next/Beta homepage Playground.
Severity: High for this flow because accepting the suggestion replaces the page with a runtime error.
Frequency: One observed attempt.
Consequence: The seeded suggestion cannot be accepted and the Playground becomes unusable until reload.

Additional information

Exact host, commit, browser, OS, and package versions are not visible in the recording. The homepage route is inferred from matching current source. The recording establishes the action and failure, but not the root cause.

Related issues checked:

• [Beta]: Homepage block drag and drop crashes with removeChild RuntimeError #5070 has the same DOM exception after homepage block drag-and-drop, but a different trigger.
• NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node. #3531 has the same exception text on Plate 38 with a different setup and no suggestion-accept repro.

Video evidence:

[zbeyens]

Fixed and verified in the current local checkout.

Proof:

• Added a Chromium regression covering the seeded homepage suggestion card: open the discussion, hover Delete, accept it, verify the phrase and card disappear, then edit the document again.
• The Chromium regression passed three consecutive runs with no runtime errors.
• The focused suggestion package contract passed all 9 editor.update.suggestion.accept cases.
• Isolated P2 autoreview reported no actionable findings.

The current tree already contains the surviving implementation path, so I could not reconstruct the exact historical regression cause from this checkout. This is local-only: no commit or PR exists yet. Leaving the issue open for maintainer-controlled integration/closure.

[felixfeng33]

Follow-up manual retest: accepting the seeded removal suggestion still triggers the removeChild NotFoundError and crashes the editor. Keeping this open.

[zbeyens]

Local candidate complete in the current checkout; uncommitted and unpushed, so the issue remains open.

Root cause: block-discussion conditionally mounted a Radix custom popover anchor. Accepting the directly selected removal suggestion removed that anchor while Radix switched the trigger between custom-anchor and trigger-anchor trees, leaving React with a detached trigger button and producing the reported removeChild NotFoundError.

Local repair and proof:

• Keep one custom-anchor topology and fall back to the stable count trigger when no suggestion node is active.
• Tighten the browser regression to click Felix's exact red text path; keep the old count-trigger path as a separate smoke test.
• Fresh Chromium exact replay: 5/5, zero retries; text and card disappear, editor remains mounted, follow-up editing passes, and no runtime/page error occurs.
• Fresh in-app Browser replay: same final state; follow-up typing produced Collaborative Editing!; zero error logs.
• Suggestion acceptance package contracts: 9/9 passed.

This is not a shipped/fixed claim. Final completion and the completed label require replay on the eventual pushed ref.