contenteditable content is not included in form submission
OS: macOS 14.0 · Device: Desktop Any · Browser: Chrome 120.0 · Keyboard: US
Open case →Scenario
contenteditable content is not included in form submission
When a contenteditable region is inside a form, its content is not automatically included in form submission. Unlike input and textarea, contenteditable content must be manually extracted and added to the form data.
other
Scenario ID
scenario-form-integration
Details
When a contenteditable region is inside a <form>, its content is not automatically included in form submission. Unlike <input> and <textarea>, contenteditable content must be manually extracted and added to the form data.
References
- Stack Overflow: Using contenteditable fields in form submission - Form integration patterns
- Web.dev: More capable form controls - formdata event
- Drupal: Hidden form controls validation - Validation issues
Scenario flow
Visual view of how this scenario connects to its concrete cases and environments. Nodes can be dragged and clicked.
Variants
Each row is a concrete case for this scenario, with a dedicated document and playground.
| Case | OS | Device | Browser | Keyboard | Status |
|---|---|---|---|---|---|
| ce-0067-contenteditable-with-form | macOS 14.0 | Desktop Any | Chrome 120.0 | US | confirmed |
Cases
Open a case to see the detailed description and its dedicated playground.
Related Scenarios
Other scenarios that share similar tags or category.
Tags: form, chrome
required attribute is not supported for validation
The required attribute, which works on form inputs to indicate mandatory fields, is not supported on contenteditable regions. There is no built-in way to mark a contenteditable as required for form validation.
1 case
Tags: chrome
contenteditable=false dismisses selection on Android Chrome
Tapping or moving across contenteditable=false regions on Android can collapse selection or clear the caret in ways that differ from desktop Chrome.
1 case
Tags: chrome
Auto-scroll while typing in contenteditable
Browsers try to keep the caret visible by scrolling the editable container or the page. During rapid typing—especially near the bottom or right edge—scroll updates can lag, batch, or feel jarring, so the caret temporarily leaves the viewport or the view jumps unexpectedly.
3 cases
Tags: chrome
autofocus attribute does not work on contenteditable
The autofocus attribute, which automatically focuses form inputs on page load, does not work on contenteditable elements. There is no built-in way to automatically focus a contenteditable region when a page loads.
1 case
Tags: form
Browser autofill and autocomplete do not work with contenteditable
Browser autofill and autocomplete features are designed to work with form-associated elements like input and textarea, not with generic contenteditable elements. The autocomplete attribute is ignored on contenteditable elements, and browsers do not provide autofill suggestions when typing in contenteditable regions.
0 cases
Comments & Discussion
Have questions, suggestions, or want to share your experience? Join the discussion below.