Save issue - saves fine, but won't allow a second "save"

Hi - thanks for the great library! When I listen to the “saved” event, it triggers successfully, but it seems the tools stop listening. (I can no longer hilight and edit). If I trigger save a second time, I get

Uncaught TypeError: Cannot read property 'removeAttribute' of null
    at c.unmount (contentTools.js:110)
    at c.save (contentTools.js:113)
    at HTMLElement.sb.onclick (contentTools.js:946)
c.unmount @ contentTools.js:110
c.save @ contentTools.js:113
sb.onclick @ contentTools.js:946

Even if I just return without doing anything this happens. For example:

editor.addEventListener('saved', async function (ev) {
        var name, payload, regions, xhr, template;
        return true;
    });

Is the API expecting a return code or some sort of trigger to indicate success and return to an editable state?

[chronofish]

YES! Thank you! that was a super easy fix!

[anthonyjb]

Ah OK so you have a custom save button - no worries but this explains why the editors state is getting out of wack.

So if your save button is passive (as in you want the button to save the document but not exit the editing mode) then when you call save flag that you want this to be a passive save save(true).

However, if you want the save button to save the changes and exit edit mode then you need to stop the editor, something like:

editor.ignition().state('ready')
editor.stop(true)

Let me know if that helps out.