All specs
W3C Input Events L2W3CShould KnowProduct

Input Events Level 2

Input & Interaction·World Wide Web Consortium
WHY YOU NEED THIS

Required for building rich text editors (Notion, Google Docs, ProseMirror, Tiptap). The beforeinput event with inputType lets you intercept and customize every editing operation before it happens.

What It Defines

Extends InputEvent with the inputType property (insertText, insertParagraph, deleteContentBackward, formatBold, etc.) and beforeinput/input events for contenteditable and textarea/input. Defines the data and dataTransfer properties for rich text operations.

Canonical (Normative)

Convenient (Practical)

inputcontenteditablerich-texteditorbeforeinputbrowser
Standards Body
World Wide Web Consortium

Publishes web platform specs including CSS, accessibility, security policies, Service Workers, Web App Manifest, and many browser APIs. Also maintains some versioned HTML/DOM specs.

Visit

Related Specs

W3C UI EventsW3CMust Know

UI Events

The foundational event model that every web application uses. Understanding event propagation (capture, target, bubble), event.preventDefault(), and the difference between key and code prevents input handling bugs.

ProductInput & Interaction
Details
W3C Clipboard APIW3CNiche

Clipboard API

Required for any 'Copy to clipboard' button, paste-from-image, or rich text editing. The async API requires user gesture and permissions — understanding the security model prevents frustrating clipboard failures.

ProductBrowser Platform
Details
W3C Selection APIW3CNiche

Selection API

Required for rich text editors, annotation tools, and any feature that reads or manipulates text selection. The Selection/Range model is how browsers track cursor position in contenteditable regions.

ProductInput & Interaction
Details