In the Ediiting taskforce of the Webapps WG of the W3C we have been looking at how the native browser undo stack is used in contenteditable in different projects. The result has been that it's not being used and that it's rather useless.
One exception has been draft-js, where the native undo seems to be used for spell-checking fixes.
It would be interesting if you could comment about what browsers/OSs you find this useful for and what you would need if the native undo stack would be disabled for contenteditable.
In the Ediiting taskforce of the Webapps WG of the W3C we have been looking at how the native browser undo stack is used in contenteditable in different projects. The result has been that it's not being used and that it's rather useless.
One exception has been draft-js, where the native undo seems to be used for spell-checking fixes.
It would be interesting if you could comment about what browsers/OSs you find this useful for and what you would need if the native undo stack would be disabled for contenteditable.
The issue is here [1].
[1] https://github.com/w3c/editing/issues/150