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

Do we really need to be done by declarative way, `contenteditable-disabled`?
How about imperative way `Document#disableCommand(name)` to disable command for current document to simplify `designMode` and nested case?

-- 
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-426559226

Received on Wednesday, 3 October 2018 08:50:07 UTC