So, after discussing this colleagues, we'd like to suggest using the new intermediate edit events vs change events instead of onFinishEditing_, which was always a bit of a hacky solution and might be a candidate for deprecation—see issue #2496 for some discussion about this, and PR #7151 for the implementation of the new events.

Let us know if you think that approach might meet your needs, as we're not sure we want to add further support fro onFinishEditing_ at the current time.

Thank you, I'll have a look.

It did seem quite natural to have some control over the final value set by the field (i.e. as argued in #2496 (comment))

If I understand correctly, the suggested approach is to handle events at the block level as opposed to at the field level. Does this mean adding an event handler via setOnChange to every block that uses the field?

This could probably work, but having it close to the field seemed logical thus far. On a related note, I was having some difficulty "merging" several onchange handlers, i.e. adding one to a block that already uses one as part of another extension. It's quite possible there's an obvious method that I missed though :)

If I understand correctly, the suggested approach is to handle events at the block level as opposed to at the field level. Does this mean adding an event handler via setOnChange to every block that uses the field?

You could do that! Or you could add one handler at the workspace level that iterates over all of the relevant blocks.

I was having some difficulty "merging" several onchange handlers, i.e. adding one to a block that already uses one as part of another extension. It's quite possible there's an obvious method that I missed though :)

Yeah there's not a good way to do this at the moment :/ we have similar problems with other mixins.

Thank you!