Re: [w3c/editing] Clarify the nested case of `contenteditable=true` and `contenteditable=plaintext-only` (Issue #470)

From TPAC 2024 Minutes:

> [#470](https://github.com/w3c/editing/issues/470)
> Johannes: What happens if contenteditable=true/plaintext are nested?
> 
> Dan: The outer one takes precedence. You can reset with contenteditable=false
> 
> Ryosuke: Same true for Webkit
> 
> Sanket: We should write this down in a spec. Current definition looks incomplete:
> https://html.spec.whatwg.org/multipage/interaction.html#editing-host
> 
> Resolution: follow model of outermost wins. File issue with HTML spec (Olli takes responsibility). 
> 
> Dan: In both examples below, they should be richtext. 
> 
> 
> Resolution: Bug will need to be filed with Chromium (Dan)/Webkit (Ryosuke).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/470#issuecomment-2397142329
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/470/2397142329@github.com>