- From: Malte Timmermann <malte_timmermann@gmx.com>
- Date: Fri, 23 Oct 2020 12:14:01 +0200
- To: public-editing-tf@w3.org
Hi, I am new here. I stumbled over the draft for ContentEditableDisabled while again searching for a solution to hinder extensions writing in the DOM of our editing web application. We use ContentEditable only to get key/IME events and cursor traveling. We (try to) hinder the browser to make any changes to the DOM on it's own. The reason is that we use the concept of "operations", and if somebody else but our own code manipulates the DOM, the positions from operations become invalid. https://www.slideshare.net/Malte.Timmermann/ox-documents-explained ContentEditableDisabled could be THE solution for our problem. Unfortunately, simple text manipulations seem to be out of scope of the ContentEditableDisabled API. I am pretty sure there are many Apps out there who could benefit of disabling all unwanted DOM manipulations including simple key input. CKEditor must have the same problem, not sure how Jira implements the collaborative editing. In the end, every app that manipulates rich content in a collaborative way could benefit. Do you think it would be reasonable to add insertCharacter(s) and deleteCharacter(s) (or "text" instead of "character" ) to the DOMCommandTokenList? Might look strange for people on first glance, but in certain scenarios this is a critical thing. Best regards, Malte.
Received on Friday, 23 October 2020 21:15:03 UTC