์ผ€์ด์Šค ce-0077 ยท ์‹œ๋‚˜๋ฆฌ์˜ค scenario-web-components-integration

contenteditable behavior differs inside Web Components

OS: Windows 11 ๊ธฐ๊ธฐ: Desktop or Laptop Any ๋ธŒ๋ผ์šฐ์ €: Chrome 120.0 ํ‚ค๋ณด๋“œ: US ์ดˆ์•ˆ
web-componentscustom-elementschromewindows

์ด ํŽ˜์ด์ง€๋Š” ์•„์ง ๋ฒˆ์—ญ๋˜์ง€ ์•Š์•˜์Šต๋‹ˆ๋‹ค

ํ˜„์žฌ ์˜์–ด ์›๋ฌธ์„ ํ‘œ์‹œํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ๋ฒˆ์—ญ์— ๊ธฐ์—ฌํ•ด ์ฃผ์‹œ๋ฉด ๊ฐ์‚ฌํ•˜๊ฒ ์Šต๋‹ˆ๋‹ค.

Phenomenon

When a contenteditable element is inside a Web Component (custom element), its behavior may differ from when itโ€™s in standard HTML. Event handling, selection, and focus management may be affected by the componentโ€™s shadow DOM or encapsulation.

Reproduction example

  1. Create a custom Web Component.
  2. Inside the component, create a contenteditable div.
  3. Try to interact with the contenteditable (type, select, etc.).
  4. Observe event handling and selection behavior.
  5. Compare with a contenteditable outside the component.

Observed behavior

  • In Chrome on Windows, contenteditable behavior may differ inside Web Components.
  • Events may not bubble correctly through shadow DOM boundaries.
  • Selection may be affected by encapsulation.
  • Focus management may be inconsistent.

Expected behavior

  • contenteditable should behave identically inside and outside Web Components.
  • Events should work correctly across shadow DOM boundaries.
  • Selection and focus should work consistently.

Playground for this case

Use the reported environment as a reference and record what happens in your environment while interacting with the editable area.

Reported environment
OS: Windows 11
Device: Desktop or Laptop Any
Browser: Chrome 120.0
Keyboard: US
Your environment

Use this editable area to reproduce the described case.

Event log
Use this log together with the case description when filing or updating an issue.
0 events
Interact with the editable area to see events here.