[Feature request] Clear undo/redo history

[AgentSmith0]

Jodit Version: 3.15.2

Browser: All
OS: All
Is React App: False

Is there any way to clear the undo/redo history? If not, is it possible to implement this feature?

[ulfw]

I have implemented this as an event that is fired externally

    editor.events.on('editor.clearHistory', () => {
        editor.observer.stack.clear();
    });

[AgentSmith0]

Thanks @ulfw, unfortunately, this doesn't work always in my case: When I set the editor value via editor.value, clear the stack, change the editors text to another value and clear the stack again, the undo button still appears, but doesn't do anything.

[xdan]

@AgentSmith0
Try that

editor.events.on('editor.clearHistory', () => {
        editor.observer.clear();
});

[AgentSmith0]

@xdan Hm, still the same problem...

[ulfw]

I had the same problem when reloading page with cleared history, but clicking into the editor window disabled the undo/redo buttons. Maybe setting focus to th editor again will solve?

[xdan]

@AgentSmith0 @ulfw The Observer module is asynchronous, i.e. it does not process the change immediately, but only processes the last one in n milliseconds. This is done so that, for example, words when you enter them get into the history of changes, and not every letter.
The observer interface does not have methods to hang a handler on a change. I'll think about how best to do it, but for now you can do a little hack

const editor = Jodit.make({
    observer: {
       timeout: 100
    }
});
editor.value = 'test';
editor.async.setTimeout(() => {
     editor.observer.clear();
}, 150);

[xdan]

Maybe when called

editor.value = 'test1';
editor.value = 'test2';

the history handler must be called immediately

[xdan]

@ulfw @AgentSmith0
Look at this release https://github.com/xdan/jodit/releases/tag/3.15.3

[AgentSmith0]

I seems to fail only when a specific string is set as value before...
I need some time to look at this, but I think it is definitely better than before. It works on every "normal" case.
Thank you very much for the new release!

[xdan]

@AgentSmith0 Can you show this specific string?

[AgentSmith0]

Sorry, I tested again and the string value is not the problem. It seems to be still a timing problem... I will test this behaviour.

[AgentSmith0]

I tried again with version 3.16.1 and it works fine now...
I don't really know the reason for this, but I will keep my eye on it.
Thank you very much!