fix(editor): use native drag events on anchorElem for full-width drop targeting

[zacharias-ona]

Problem

Follow-up to #100 — the vertical dead zone fix didn't address the real issue. The drag handle sits in the anchorElem's 32px left padding, outside the Lexical contentEditable. Lexical's DRAGOVER_COMMAND / DROP_COMMAND only fire when the cursor is over the contentEditable, so dragging straight down or slightly left from the handle never triggers the drop indicator. The user has to move the cursor right into the text area for the drop to register.

Root cause

<div class="relative -ml-8 pl-8">   ← anchorElem (full width, 32px left padding)
  [drag handle]                      ← lives in the padding zone
  <ContentEditable />                ← Lexical events only fire here
</div>

Lexical dispatches DRAGOVER_COMMAND / DROP_COMMAND from its own event listeners on the contentEditable element. The drag handle and the padding area to its left are outside that element, so native drag events in that zone are never forwarded to Lexical's command system.

Fix

• Replace Lexical DRAGOVER_COMMAND / DROP_COMMAND handlers with native dragover / drop listeners on the anchorElem — this covers the full container width including the handle area
• Skip the horizontal bounds check during drag (useUnboundedSearch) so the cursor can stay in the handle column
• Remove unused Lexical imports (COMMAND_PRIORITY_HIGH, DRAGOVER_COMMAND, DROP_COMMAND, mergeRegister)

Closes #99

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
memo	Ready	Preview, Comment	Apr 16, 2026 6:55pm

[zacharias-ona]

[shepherd] Closing — issue #99 is already closed. This PR is a duplicate.