[w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150)

The subject  of removing the undo manager functionality from contenteditable by default came up at the Editing Taskforce F2F meeting on 2016-09-22 at TPAC in Lisboa, Portugal. It was pointed out that the browser's undo stack would be entirely useless once the JS editor interrupt the default behavior even in just a few limited cases. No-one present opposed the idea of removing the browser's undo functionality for contenteditable and replacing it by a way for the JS to enable/disable the menu entries for redo and undo + giving the ability to listen for redo/undo being triggered via beforeinput events.

Everyone agreed to turn this functionality of by default. (given that there seems to be no authoritative spec that says that undo IS provided, we may only need to spec that undo is turned off be default).

In addition, the following JS editor projects were contacted and **all** of them responded that the browser's undo stack and default undo behavior was either **useless** or **harmful**:

* CKeditor
* ProseMirror
* QuillJS
* ContentTools library
* Substance.io

The following applications were investigated and it was determined that they do not use the browser's undo stack for contenteditable either:

* Gmail
* Office 365
* Facebook's various input fields
* Google Docs (only using very limited amount of contenteditable anyway)




-- 
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/150