Issue Bug Closed

#106907EXT:form form editor always recognizes form as dirty, shows "unsaved changes" popup when leaving

Garvin Hicking 06/18/25, 12:37 updated 08/12/25, 14:36

Description

  • Edit a backend EXT:form form
  • Ensure a FINISHER is added of either “Email to Sender” or “Email to receiver”
  • Enter some dummy values
  • Save the form
  • “Close” the form, and see the modal that says “unsaved changes”

This does not happen for other Core finishers.

I believe the error comes from the specific 2 finishers having the “add row” option for recipients. My feeling is that this initializes JS events which trigger the ‘Dirtyness’ of the form. And once this is restored, the form editor will always think this initialized section is now ‘dirty’ even though it holds the same changes.

The dirty state is triggered via Build/Sources/TypeScript/form/backend/form-editor/mediator.ts – method getPublisherSubscriber().subscribe('core/formElement/somePropertyChanged', (...).

Maybe it’s a workaround to compare if old/new state are really the same to only conditionally execute

getFormEditorApp().setUnsavedContent(true);

This behaviour was caused by #106485 in v13.4.14 (works in 13.4.13) – probably it popuplates/executes the event above.

Reviews 2