Re: [w3c/editing] contenteditable-disabled (#176)

There's `execCommand()` already and it was used to disable some features (like table editing handlers). I don't think this would be confusing to anyone. 

>From my point of view, the biggest problem with a declarative mechanism is that it may be limiting in the future if the configuration would need to become more complicated. Other than that, it seems ok.

-- 
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/176#issuecomment-426793868