Conversation
- Add dedicated TextSelectionOverlay (single selection only) - Hide DOM overlay when WASM backend + text edit mode (WASM highlight only) - Branch SingleSelectionOverlay on tspan to use TextSelectionOverlay - Keeps text overlay logic trackable in one entry point Co-authored-by: universe <[email protected]>
|
Cursor Agent can help with this pull request. Just |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
5 Skipped Deployments
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
2 participants
Add
TextSelectionOverlayto manage text node selection, centralizing text-specific overlay logic and ensuring proper rendering when editing text in WASM.When editing text with the WASM backend, the DOM overlay was redundant and could cause visual discrepancies with the WASM-rendered outline. This change introduces a dedicated overlay component for text nodes that hides the DOM frame in such cases, ensuring only the WASM outline is visible and in sync.