Open asikpradhan opened 7 years ago
Hey,
Have you found any solution for this? I am facing the same issue.
Unfortunately, we won't be fixing this in the near future.
We're now focusing on our commercial track-changes plugin, which is based on a newly written tracking engine. Among many changes, list tracking is done properly there.
In case someone wants to fix the problem, here's the gist of it: The list plugin intercepts keyboard events and changes the DOM in cases like deleting the first item of a list, erasing a whole list, converting list items to paragraphs and more. These changes do not go through ckeditor, neither as commands nor as events. Therefore, this tracking engine has no chance of even knowing about these events, let alone handle them.
One viable approach would be to listen to DOM mutations and try to sort out the markup to reflect the changes.
Create an ordered list, then if you try to delete the whole list as a different editor, it deletes it instead of tracking the change.
This happens for unordered list as well.