scenario-composition-events
Composition events are not fired consistently for all IMEs
Open scenario →A scenario groups multiple cases that describe the same phenomenon across different operating systems, devices, browsers, or keyboard setups.
Composition events are not fired consistently for all IMEs
Open scenario →Backspace removes a whole composed syllable instead of a single jamo
Open scenario →Composition is cancelled when pressing Enter inside contenteditable
Open scenario →IME candidate window appears in wrong position
Open scenario →Space key during composition is ignored or committed inconsistently
Open scenario →Undo during IME composition clears more text than expected
Open scenario →Baseline typing and composition in a simple contenteditable region
Open scenario →execCommand is deprecated but still widely used for formatting
Open scenario →Bold formatting is lost when typing after applying bold
Open scenario →insertHTML breaks DOM structure and formatting
Open scenario →Pasting rich text into contenteditable strips markup unexpectedly
Open scenario →Pasting rich text inserts unwanted formatting
Open scenario →Caret position jumps unexpectedly after pasting content
Open scenario →Clipboard API paste does not work in contenteditable
Open scenario →preventDefault on paste event does not prevent default paste behavior
Open scenario →Pasting images into contenteditable is not supported consistently
Open scenario →Selection is lost after copying content in contenteditable
Open scenario →CSS contain property may affect contenteditable selection
Open scenario →CSS transform may cause selection handles to appear in wrong position
Open scenario →Drag and drop of text within contenteditable does not work as expected
Open scenario →Touch events interfere with contenteditable focus on mobile
Open scenario →Nested contenteditable elements cause focus and selection issues
Open scenario →window.getSelection() returns null when contenteditable loses focus
Open scenario →Selection collapses unexpectedly when clicking outside contenteditable
Open scenario →Selection range is incorrect when selecting across multiple elements
Open scenario →Touch selection handles are difficult to use on mobile devices
Open scenario →Virtual scrolling libraries interfere with contenteditable selection
Open scenario →Arrow keys move by word instead of character when modifier is not pressed
Open scenario →Arrow keys skip over emoji in contenteditable
Open scenario →autocapitalize attribute works inconsistently on contenteditable
Open scenario →autocorrect attribute behavior differs on contenteditable
Open scenario →CSS backdrop-filter may cause rendering issues in contenteditable
Open scenario →enterkeyhint attribute does not work on contenteditable
Open scenario →enterkeyhint and inputmode affect Enter key behavior inconsistently
Open scenario →inputmode attribute does not affect virtual keyboard on mobile
Open scenario →Media query layout changes may disrupt contenteditable editing
Open scenario →Virtual keyboard on mobile scrolls contenteditable out of view
Open scenario →Screen readers do not announce changes in contenteditable regions
Open scenario →ARIA attributes on contenteditable are not properly announced
Open scenario →CSS filter may affect contenteditable performance
Open scenario →CSS will-change may improve or degrade contenteditable performance
Open scenario →MutationObserver may interfere with contenteditable editing
Open scenario →Typing becomes slow with large contenteditable content
Open scenario →ResizeObserver may cause layout shifts during contenteditable editing
Open scenario →autofocus attribute does not work on contenteditable
Open scenario →Focus is lost when clicking on certain elements within contenteditable
Open scenario →Fullscreen API may affect contenteditable focus and selection
Open scenario →Page Visibility API may affect contenteditable during tab switches
Open scenario →Placeholder text disappears when contenteditable receives focus
Open scenario →tabindex attribute does not control focus order correctly
Open scenario →Autocomplete suggestions do not appear for contenteditable
Open scenario →Backspace deletes whole words instead of single characters
Open scenario →beforeinput event is not supported in Safari
Open scenario →contenteditable behavior differs when inside an iframe
Open scenario →contenteditable inheritance behavior is inconsistent
Open scenario →contenteditable="false" on child elements is not respected consistently
Open scenario →contenteditable does not work correctly inside Shadow DOM
Open scenario →contenteditable in table cells causes layout issues
Open scenario →CORS restrictions may affect contenteditable in cross-origin iframes
Open scenario →Content Security Policy may restrict contenteditable behavior
Open scenario →CSS isolation property may affect contenteditable stacking context
Open scenario →CSS mix-blend-mode may affect contenteditable text rendering
Open scenario →Delete key behavior is inconsistent with Backspace
Open scenario →disabled attribute does not disable contenteditable
Open scenario →Pressing Enter inserts two line breaks in contenteditable
Open scenario →Drag and Drop API behavior differs in contenteditable
Open scenario →File API drag and drop does not work in contenteditable
Open scenario →contenteditable content is not included in form submission
Open scenario →Input events fire multiple times for single keystroke
Open scenario →IntersectionObserver may affect contenteditable visibility detection
Open scenario →lang attribute does not affect spellcheck language
Open scenario →maxlength attribute is not supported on contenteditable
Open scenario →pattern attribute does not validate contenteditable content
Open scenario →readonly attribute does not prevent editing in contenteditable
Open scenario →required attribute is not supported for validation
Open scenario →Spellcheck interferes with contenteditable editing
Open scenario →Spellcheck suggestions interfere with contenteditable editing
Open scenario →Text direction (dir attribute) changes are not applied during editing
Open scenario →Undo and redo behavior is inconsistent across browsers
Open scenario →contenteditable behavior differs inside Web Components
Open scenario →XSS protection may interfere with contenteditable HTML insertion
Open scenario →