fix(wysiwyg): Implement programmatic rendering to eliminate focus loss during typing
- Convert parent component to use static rendering with programmatic DOM manipulation - Remove all reactive state that could trigger re-renders during editing - Delay content sync to avoid interference with typing (2s auto-save) - Update all block operations to use manual DOM updates instead of Lit re-renders - Fix specific issue where typing + arrow keys caused focus loss - Add comprehensive focus management documentation
This commit is contained in:
@@ -409,4 +409,61 @@ Created `wysiwyg.interfaces.ts` with proper typing:
|
||||
4. Arrow keys handle block navigation without focus loss
|
||||
5. All timing is handled via proper async/await patterns
|
||||
|
||||
The refactoring eliminates race conditions and timing issues that were causing focus loss and content duplication problems.
|
||||
The refactoring eliminates race conditions and timing issues that were causing focus loss and content duplication problems.
|
||||
|
||||
### Programmatic Rendering Solution (2025-06-24 - Part 10)
|
||||
|
||||
Fixed persistent focus loss issue by implementing fully programmatic rendering:
|
||||
|
||||
#### The Problem:
|
||||
- User would click in a block, type text, then press arrow keys and lose focus
|
||||
- Root cause: Lit was re-rendering components when block content was mutated
|
||||
- Even with shouldUpdate() preventing re-renders, parent re-evaluation caused focus loss
|
||||
|
||||
#### The Solution:
|
||||
|
||||
1. **Static Parent Rendering**:
|
||||
- Parent component renders only once with empty editor content div
|
||||
- All blocks are created and managed programmatically via DOM manipulation
|
||||
- No Lit re-renders triggered by state changes
|
||||
|
||||
2. **Manual Block Management**:
|
||||
- `renderBlocksProgrammatically()` creates all block elements manually
|
||||
- `createBlockElement()` builds block wrapper with all event handlers
|
||||
- `updateBlockElement()` replaces individual blocks when needed
|
||||
- No reactive properties trigger parent re-renders
|
||||
|
||||
3. **Content Update Strategy**:
|
||||
- During typing, content is NOT immediately synced to data model
|
||||
- Auto-save delayed to 2 seconds to avoid interference
|
||||
- Content synced from DOM only on blur or before save
|
||||
- `syncAllBlockContent()` reads from DOM when needed
|
||||
|
||||
4. **Focus Preservation**:
|
||||
- Block components prevent re-renders with `shouldUpdate()`
|
||||
- Parent never re-renders after initial load
|
||||
- Focus remains stable during all editing operations
|
||||
- Arrow key navigation works without focus loss
|
||||
|
||||
5. **Implementation Details**:
|
||||
```typescript
|
||||
// Parent render method - static after first render
|
||||
render(): TemplateResult {
|
||||
return html`
|
||||
<div class="editor-content" id="editor-content">
|
||||
<!-- Blocks rendered programmatically -->
|
||||
</div>
|
||||
`;
|
||||
}
|
||||
|
||||
// All block operations use DOM manipulation
|
||||
private renderBlocksProgrammatically() {
|
||||
this.editorContentRef.innerHTML = '';
|
||||
this.blocks.forEach(block => {
|
||||
const blockWrapper = this.createBlockElement(block);
|
||||
this.editorContentRef.appendChild(blockWrapper);
|
||||
});
|
||||
}
|
||||
```
|
||||
|
||||
This approach completely eliminates focus loss by taking full control of the DOM and preventing any framework-induced re-renders during editing.
|
Reference in New Issue
Block a user