Missing Loading Indicator & Disabled UI on Save/Publish Actions in Backoffice

[okadriu]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.3.0-rc2 (also present in 15.2.3)

Bug summary

When saving or publishing a content node in the Umbraco backoffice, the UI does not provide any visual indication that the action is in progress. In previous versions (e.g., Umbraco 13), a loading spinner was displayed on the buttons, and the UI was disabled to prevent accidental changes during the process.

Currently, the UI remains fully interactive while the operation is in progress, making it unclear whether the save/publish action is happening or not. The only feedback comes after several seconds when the success toast notification appears.

Specifics

• This occurs when clicking the "Save" or "Save and Publish" buttons in the backoffice content editor.
• The issue is reproducible in Chrome, Edge, and Firefox.
• No visible console errors related to this issue.
• Attached is a video demonstrating the issue.

missing-loading-indicator-and-disabled-ui.mp4

Steps to reproduce

• Open any content node in the backoffice.
• Click "Save" or "Save and Publish".
• Observe that there is no loading indicator or UI feedback during the process.
• After several seconds, a toast notification appears confirming the action.

Expected result / actual result

Expected Result:

• A loading indicator should appear on the Save and Save and Publish buttons while the action is in progress.
• The content editor should be temporarily disabled during the operation to prevent unintended modifications.

Actual Result:

• There is no loading indicator on the buttons.
• The content editor remains fully interactive, allowing changes while the operation is still in progress.

[github-actions]

Hi there @okadriu!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂