RenameFile

DogmaDragon · June 27, 2026, 8:58pm

fix(RenameFile): prevent scene title freezing on Next navigation

main ← garfolino:fix/renamefile-title-stuck

opened 07:21PM - 27 Jun 26 UTC

## Problem When the RenameFile plugin is active on a scene detail page, pressin…g **Next** to navigate to another scene leaves the **previous** scene's title displayed. Every other field updates correctly; only the title is frozen. Disabling the plugin restores normal behavior. **Root cause:** The scene title is rendered by a React-controlled `TruncatedText` component. `wrapElement()` replaced its contents with an `<a>` element via `element.innerHTML = ''`, which detaches the text node React tracks. On navigation, React writes the new title into that now-orphaned node, so the visible title never updates. This is a DOM-ownership conflict, not a caching issue (reproduces across browsers). ## Solution Stop restructuring React's DOM. Instead: - **Event delegation** — a single `document`-level `click` listener resolves the title via `event.target.closest('.scene-header div.TruncatedText')` and reads the text at click time. React renders/updates the title freely; we never touch its structure. - **Non-destructive affordance** — the `.renamefile` class and tooltip are applied via `classList.add` / `setAttribute` only (no child mutation), so React's text node stays intact. - **CSS** — `.renamefile` now uses `cursor: pointer` + hover underline on the title element itself. All four interaction modes (click / Ctrl / Shift / Alt) are preserved through the unchanged `AppendTitleField`. Version bumped `1.0.0` → `1.0.1`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

@David-Maisonave would you be interested in reviewing it?