Big issue with cloneable fields

In your screenshot you do not look like you tried to save it with valid values

Ok I rechecked and the issue is now just my own JS. But please see the video so I can demonstrate that how I validate with JS now no longer works: https://jam.dev/c/f8d9026d-9e20-47ed-80bb-6d98f61df7ee

Staging site was created just now, but the only difference is the MB versions (staging is latest)

So this check no longer works?

    
!$('input[name="academicfindings[0][academicfinding]"]').val().trim()) { ....} 

Has the index changed perhaps? Or a way to check validation in js ?

But as shown in the video, it was working and just the MB change that is failing this test.

(And I must admit that I assumed the new version was not working as this js was not working when I tested it - and this js not working was a symptom of when it didn't work in the last version, but it does submit now - just the js)

Understand that the issue I faced in 5.10.1 was due to the index changing. Did the indexs change for other things too? Eg - taxonomies? I have a lot of code that grabs the first index in custom ways. Was it just cloneable fields the index changed for? Are they likely to change again?