- From: Johannes Wilm <notifications@github.com>
- Date: Sun, 03 Feb 2019 11:59:06 -0800
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 3 February 2019 19:59:27 UTC
> Typically, a rich-text editor which supports operational transformation or other real-time collaborative engine will have its own undo manager and know what can be undone (usually, the current user's changes only). Additionally, the undoing may not correspond exactly to what had been changed in the first place. So for example if you have something like: User 1 writes a word: > The fish are **exppensive**|. User 2 corrects the word: > The fish are ex~p~pensive. User 1 undoes his latest change. This can either be entirely forbidden, as it interferes with the changes of user 2, or it could for example be to delete the new word: > The fish are ~expensive~. What is possible is a decision that has to be taken fairly close to the final app user / person who runs the website as there are many factors to that decide what makes most sense. It can have to do with the kinds of users and the kinds of texts one is dealing with. > So as long as the decision is in JS editor's "hands" we should be fine. Agreed. Very important that we leave the decision to JS as otherwise it will likely just be ignored/overridden as is the case today. -- 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#issuecomment-460083003
Received on Sunday, 3 February 2019 19:59:27 UTC