XB UI doesn't save the media/image or fields that involve Drupal javascript.

The media library part might be resolved by 📌 [PP-1] Handle media image fields on page data form Postponed . I'm wondering if there are other types of fields we should be looking into?

I found this very hard to understand 😅 Some terminology is off. I think this is what you meant?

This sounds connected to ✨ [PP-1] Make link widget autocomplete work (for uri and uri-reference props) Postponed and 📌 Confirm Semi-coupled form elements can work with autocomplete Active .

I'd go further than @lauriii in 📌 [PP-1] Handle media image fields on page data form Postponed — AFAICT this is a duplicate of 📌 [PP-1] Handle media image fields on page data form Postponed and 📌 Confirm Semi-coupled form elements can work with autocomplete Active .

@amangrover90: Please check those 2 issues and confirm they report the same problem. If so, please close this issue in favor of those 2 more tightly scoped issues, and tag them .

@wimleers I checked both the issues, while these issues do address media/image fields and autocomplete fields, I'm not sure if it'll be enough to provide a fix for the fields that don't involve AJAX and just involve client side JS. e.g. generating a tag based on title; generating the path field based on title or any text field whose input is being set by the client side JS.

A good example to check this out could be; adding a field to an entity type e.g. summary field and updating summary based on what user types into body field by picking up first 50 words using client side JS. OR simply updating path field based on title like we were doing in https://www.drupal.org/project/experience_builder/issues/3499960 ✨ Creating a page generates the URL path dynamically when editing. Active . The JS attached to the form does update the field value but it didn't get saved in the redux state. So if one types anything in any other field or just clicks on Publish, those changes are lost.

All in all, XB UI needs to respect the JS behaviors attached to the Form by Drupal. So I think this issue is still needed to fix this for any kind of field that comes up with its own JS behaviors.

I know I'm talking somewhat generically but hope it makes sense.

FYI: escalated to @effulgentsia, to decide when to get time from Ben/Bálint to work on this problem space.