Re: [w3c/editing] undo manager (#209)

Firstmost, excuse me, but I haven't read undo manager / undo API draft, so I might be missing something.

Answering @Reinmar question: yes, in CKE5, we would have to do some, potentially time-consuming, evaluations to know if undo execution is actually going to make any changes in content. AFAIR, other popular editors also have this "problem" that sometimes undo does nothing.

However, this does not have to be true for all editors. Maybe there's a RTC solution, based on something other than OT (and probably less complex than what we have in CKE5) that does not need that much evaluation.

By the way, reading this thread one things got my attention: why are we talking about real-time collaboration? Every editor will have its own set of features, own internal data models, own way to solve real-time collaboration and own data format. I simply can't see what we could have in undo API that would 1) help editor developers and 2) be general enough to fit all the solutions.

But even apart of that, undo is a local "thing", that should be limited only to changes done on one browser/client. Having a common undo stack for all the clients is a UX nightmare and I'd see this as a cardinal error in designing and developing a real-time collaborative editor.

-- 
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/209#issuecomment-531802453