Re: [w3c/editing] INPUT/TEXTAREA should support subset of execCommand (#160)

>     I have no idea how to manage undo stack separately for each contenteditable element.
> 
> Just being able to entirely disable the undo stack for a contenteditable element would help, because then one doesn't have to worry about undo events coming in while the selection is in another element on the page. In that case it would be important that browser native buttons for undo and redo can be enabled/disabled by means of JavaScript.

Sounds like there should be a command to disable/enable undo of HTML editors?

>     If there is no contenteditable="false", it could be though...
> 
> I don't think I understood this sentence.

For example,

```
<div contenteditable>
  <p><br></p>
  <div contenteditable="false">
    <p>Something: <span contenteditable>value</span></p>
  </div>
</div>
```

`<span contentediable>` can be modified when both: `[div contenteditable]` has focus and `[span contenteditable]` has focus. So, browser cannot associate each edit operation to which editing host's undo stack. Even if it always associated into the innermost editing host, that causes users cannot undoing changes in `<span contenteditable>` when they tries to undo if `<div contentediable>` has focus. 

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