Saving BlockGrid Areas Settings instable

[idseefeld]

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

v15.3.0-rc2

Bug summary

I have created two Block Grid Document Types (Element Types) for layout areas. In the Block Grid Data Type I have added the same Document Type (Element Type) to the Settings model and configured different column settings in Areas.
The Settings model Element Type has three properties of types: Media Picker, Color Picker and Toggle.
In the Content area I created a content node and added both layouts to the Block Grid property.

The issue is now:

When I edit the settings they are not always adopted. Sometimes it happens the Update Button shows the delay state and the edit layer does not close automatically. This signals already that the change where not properly submitted. Opening the editor proves this too.

Specifics

Document Types are in the document-element-types.zip:
document-element-types.zip

Screenshots of the Block Grid Data Type:

Steps to reproduce

1. Reproduce the described setup.
2. Edit first setting. The Update button should behave normal and the editor layer closes automatically
3. Edit the second setting and the Update buttons will show the delayed state and the editor layer does not close automatically.
4. Save and Publish
5. The first edit even when you take the second item first should work again, but now editing the other item will fail again.

There is no error in DevTools console and the only hint in verbose mode might be: [Violation] Forced reflow while executing JavaScript took <N>ms

I guess the issue has to do with state handling or caching.

---

This item has been added to our backlog AB#50639

[github-actions]

Hi there @idseefeld!

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 🤖 🙂