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

@Reinmar's suggestion would cover all usecases I have come across so far. I am not so sure of what it gives of added benefit when compared with the current solution though, unless we plan on expanding with more options than just enable/disable some day.

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

Received on Wednesday, 3 October 2018 09:36:51 UTC