Overview
Steps To Reproduce
- Enable
xb_test_article_fieldsmodule and add an article node - Edit this article in XB and click 'Add another item' on the multi value text widget And Populate the field as "Test".
- Wait for the autosave to be stored
- Click 'Add another item' on the multi value text widget And Populate the field as "Testing".
- Click on Preview
- Click on Exit Preview : Here "Testing" field is gone now
Proposed resolution
User interface changes
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 3536214mov.mov | 7.64 MB | neha_bawankar |
| Screen Recording 2025-07-16 at 12.10.46 PM.mov | 10.9 MB | neha_bawankar |
Comments
Comment #2
wim leersThanks!
Original bug testing report: #3514900-24: EntityFormController should load auto-save state if it exists.
Comment #3
larowlanlooks like more form cache/build ID shenanigans
I wonder if this still occurs after #3533289: Page data form values-in-progress not retained for Media Library (and perhaps other) fields - are you able to re-test @neha_bawankar ?
Comment #4
wim leersIs this a duplicate of #3521641: AJAX race condition: implement form cache locking protection between the ApiLayoutController and the EntityFormController? 🤔
Comment #5
wim leersPinged Neha :)
Also: this sounds very closely related to what #3521641: AJAX race condition: implement form cache locking protection between the ApiLayoutController and the EntityFormController predicted? 🤓
Comment #6
lauriiiComment #7
larowlanI think #3533289: Page data form values-in-progress not retained for Media Library (and perhaps other) fields could have solved this, we didn't invalidate the entity form cache in the front-end enough before that
Comment #8
wim leersNeha, could you check if this is still relevant? See #7 for why. Thanks! 🙏
Comment #9
neha_bawankar commentedTested changes on branch 1.x , the above reported issue is not reproducible
Comment #10
wim leersYay, thanks @neha_bawankar!