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

> The solution there seems to be adding the ability to add custom actions to the native menus, but that will need to be dealt with in a separate issue. This was also briefly discussed at TPAC 2017.

Assuming that we can't get access to undo/redo and clipboard's content, this indeed seems to be the solution. We can't completely hide native controls (those floating balloons) because we wouldn't have access to the clipboard, so adding our items to these menus seems to be the only way around. 

However, until we get access to native menus, the situation won't be much better for us than it's now. We'll certainly disable all native actions we can, but we'll still have to fight with native menus ([1](ckeditor/ckeditor5#1107) and [2](ProseMirror/prosemirror#7)) which don't leave space for our UIs.

So, it's a step forward and I'm all for it, but alone it won't significantly help.

---

> It would be good to have a way to be able to disable all of these in one go. For example `contenteditable-disabled="all"`

Such an option may not be future-proof. If we'll ever add more options to `contenteditable-disabled` (e.g. `typing` or `clipboard` :D), then we may break applications which already use `all`. I'd use an explicit list.

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