Non-editable elements become editable on double-click in IE11
OS: Windows Any · Device: Desktop or Laptop Any · Browser: Internet Explorer 11 · Keyboard: US
Open case →Scenario
Non-editable regions and double-click to edit in IE11
Legacy IE11 had quirks when mixing contenteditable=false regions with adjacent editables—double-click could focus the wrong host or fail to enter edit mode.
input
Scenario ID
scenario-ie11-non-editable-double-click-editable
Details
Legacy IE11 had quirks when mixing contenteditable=false regions with adjacent editables—double-click could focus the wrong host or fail to enter edit mode.
Related Cases
References
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-0315-ie11-non-editable-double-click-editable | Windows Any | Desktop or Laptop Any | Internet Explorer 11 | US | draft |
Cases
Open a case to see the detailed description and its dedicated playground.
Related Scenarios
Other scenarios that share similar tags or category.
Tags: contenteditable, focus
Focus in table cells with contenteditable (legacy IE)
Internet Explorer and old EdgeHTML had specific bugs when focusing contenteditable inside table cells—caret not appearing, wrong active element, or selection stuck in adjacent cells.
1 case
Tags: contenteditable
Caret jumps to end after DOM manipulation in Chrome
In Chromium, programmatic DOM updates (normalization, wrapping, React reconciliation) while the user is typing can move the caret to the end of the contenteditable or to an unexpected boundary—especially when the mutation happens between keystrokes.
1 case
Tags: contenteditable
HTML Drag and Drop API with contenteditable
Using the HTML drag-and-drop API inside or alongside contenteditable regions often diverges from behavior on plain elements: default actions, `contenteditable` hit-testing, and `beforeinput`/`drop` ordering differ by browser. Custom editors must reconcile native DnD with their own selection model.
1 case
Tags: contenteditable
Cursor disappears near contenteditable=false boundaries in Firefox
Firefox may hide or misplace the caret when moving across contenteditable=true/false boundaries—widgets and embeds inside editors are affected.
1 case
Tags: contenteditable
getTargetRanges() can reference the wrong contenteditable when editors are nested
On some engines (notably Firefox for Android / Fenix), beforeinput getTargetRanges() may describe the outer contenteditable host instead of the inner focused editor. Custom handlers that trust targetRanges alone may delete or insert in the parent surface while the user believes they are typing in a nested field.
1 case
Comments & Discussion
Have questions, suggestions, or want to share your experience? Join the discussion below.