AI Weekly Malaysia

David Bushell documents building a browser-based text editor, first trying <canvas> rendering before switching to contenteditable="plaintext-only" for native text selection, undo history, and accessibility. He notes key gotchas like spellcheck causing input latency spikes and the inaccessibility of canvas-based text rendering.

Why: If you're building any rich-text or code-editing UI in the browser, the contenteditable="plaintext-only" approach with spellcheck/autocorrect disabled is a concrete shortcut to native selection and undo without reinventing them. The canvas approach is a dead end for accessibility.