Re: [w3c/editing] Update to a spec draft document (#251)

Stupid question... but y u no contenteditable=“disabled”? Is that because any truthy attribute value enables it? Even if so, maybe one can feature detect for it... like set it to “disabled”, if it becomes “”, then remove the attribute. Otherwise, it’s supported. Just a thought. 

-- 
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/pull/251#issuecomment-631302058

Received on Wednesday, 20 May 2020 07:49:57 UTC