HTML Docs Feature Audit — Fix Log

Root cause: The shadow DOM viewer was overwriting region content with stale data during Liveblocks sync, which reset the cursor position to the start of the contenteditable element.

Fix: Added a guard that compares incoming region content against the current DOM state before applying overwrites. If the region is actively being edited and the content hasn't meaningfully changed, the overwrite is skipped — preserving cursor position.

Root cause: The structural undo handler intercepted Cmd+Z even when the user's most recent edit was character-level (typing or paste). It used a 30-second timeout heuristic: if the structural undo stack had any entries — even from a block operation done minutes ago — it would pop a stale snapshot and revert far more than the paste.

Fix: Replaced the timeout heuristic with a precise charEditsSinceStructuralRef flag. A new onInputActivity callback fires from every character-level input event. When the flag is set, Cmd+Z falls through to the browser's native undo, which correctly handles paste reversal. Structural ops reset the flag.

Root cause: <DocumentToolbar /> was rendered without onUndo or onRedo props. The buttons appeared but did nothing on click. Keyboard shortcuts (Cmd+Z) worked separately through the shadow DOM viewer's keydown handler — the toolbar was just never connected.

Fix: Wired onUndo and onRedo callbacks that try structural undo/redo first, then fall back to document.execCommand('undo'/'redo') in the active contenteditable region for character-level edits.

Root cause: The comment resolution logic only allowed the comment author to resolve their own comments. Collaborators with edit access were blocked.

Fix: Updated the server action to allow any authenticated collaborator (with edit permissions) to resolve comments, not just the original author.

Root cause: Both Google Docs import and Generative AI creation used window.open() to open the resulting document. Ad blockers and browser settings silently block this, leaving users stranded.

Fix: Added popup-blocked detection. When the popup fails, an in-app fallback banner appears with a direct link to the new document. Users are never silently stuck.

Root cause: In edit mode, contenteditable swallows normal link clicks. There was no tooltip or alternative interaction path for links.

Fix: Added a link tooltip on hover (showing the URL) and Cmd+click to open. Links also get proper visual styling (underline, color) to indicate they're interactive.

Root cause: Portal elements created by the Docsmith panel weren't being cleaned up on unmount, leaving a small floating UI element visible in the corner.

Fix: Added proper cleanup in the panel's unmount lifecycle to remove all portal elements.

Root cause: The visual association between a comment and its highlighted text was minimal — no persistent background, no hover state linking them.

Fix: Strengthened the highlight with a persistent active background state on the text span associated with the selected comment. Hovering a comment in the panel highlights its text, and vice versa.

Root cause: The HTML validator threw an error and rejected the entire beautified output if the LLM included any <script>, <link rel="stylesheet">, <iframe>, <object>, or <embed> tags — even though the prompt already forbids them. LLMs don't always comply, especially when user instructions push toward interactivity ("form intake", "easy to copy paste").

Fix: Both validators (validateGeneratedHtml and validateGeneratedHtmlRich) now strip offending tags instead of throwing. The beautified HTML goes through with all its styling intact, minus the disallowed elements. Google Fonts links are still preserved in the rich variant.

Root cause: The inactive Docsmith icon was monochrome, blending in with other UI elements and reducing discoverability of the platform's flagship feature.

Fix: Added a subtle accent tint to the inactive icon so it stands out without being obnoxious. Active and inactive states are now visually distinct.

Root cause: Email invitations and link-sharing controls were mixed together in one view. Users couldn't tell which permission (View/Edit) applied to which sharing method.

Fix: Added a visual divider and clear section labels ("Invite by email" / "Anyone with the link") to separate the two sharing mechanisms and their permission controls.

Root cause: Long Supabase storage URLs were token-expensive for the LLM and easily dropped or mangled during the beautify/redesign transform.

Fix: New image preservation pipeline: images are extracted and replaced with short placeholders before the LLM call, then restored after. A safety net re-inserts any images still missing. Affects all callers: beautify, Google Docs/Slides import, PDF import, paste-to-document.