Improve handling of undo/redo events in web demo (#1254)

[garyg1]

Fixes #1254. In the demo on https://jsonnet.org, if you hit redo/undo for multiple characters, the demo breaks. This seems to be because the browser generates multiple text change events (Chrome 139, MacOS 14.6).

Previous Behavior

https://jsonnet.org/

Screen.Recording.2025-09-02.at.8.12.12.PM.mov

New Behavior

Screen.Recording.2025-09-02.at.8.12.43.PM.mov

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[johnbartholomew]

So if I understand correctly you're using this to serialise processing each of the change events?

I think that's ok. Though I think there's another way to do it without the setTimeout: You can keep a reference to an 'ongoing change' to await, and then chain them. Something like this:

    let ongoingChange = Promise.resolve(true);
    editor.on('change', function() {
        return ongoingChange.then(async () => {
            try {
                // previous change is complete and future changes are queued on our promise
                // do the event processing
            } catch (e) {
                // log the error; if it unwinds further then it'll break the Promise chain
            }
        });
    });

What do you think? (I haven't tried running this to verify it!)

[johnbartholomew]

Apologies, I meant to suggest chaining it like this (updating ongoingChange each time):

    let ongoingChange = Promise.resolve(true);
    editor.on('change', function() {
        ongoingChange = ongoingChange.then(async () => {
            try {
                // previous change is complete and future changes are queued on our promise
                // do the event processing
            } catch (e) {
                // log the error; if it unwinds further then it'll break the Promise chain
            }
        });
        return ongoingChange;
    });

[garyg1]

Nice! That is much cleaner.

[johnbartholomew]

Thanks for the contribution! It's great to have a fix for this!

[johnbartholomew]

Squashed, merged, and deployed to the website. Thanks for the fix!

[garyg1]

Thanks for taking a look at this!

[garyg1]

Nice! That is much cleaner.