Content language and translation AJAX expansion is backwards

HI @RoloDMonkey

I have followed the steps and able to reproduce the issue.
for debugging this issue i have added one more content type called "blog post". so it is expending the field under blog post and all the fields under newly created content type is checked. please suggest the expected behaviour ?

Expected behavior:

When the main entity type, like Article, is translatable the fields under the article should always be expanded. On the other hand, if the translatable checkbox next to an entity type is not checked then its fields should not be visible.

The fields will become visible if you are clicking the translatable checkbox for the first time, or if you turn it off and then back on again. But, they are not expanded when the page first loads. That is why I marked this as a major issue, because right now there isn't a way to accurately view and manage which fields are translatable through the UI.

I have the same issue as RoloDMonkey. I did a change in the core/modules/content_translation/content_translation.admin.js -> #7. It worked for me. I didn't do an extensive test of it. So, I don't know if it's the right way or if this opens new problems, but it worked on my project.

The Needs Review Queue Bot → tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

We applied the patch on multiple websites (also on version 10.2.2) and it seams that the patch solved that issue for us.

I applied the patch, but this initially did fix the issue. I was however also seeing a TypeError in the console (L:64 of content_translation.admin.js) as $element[0] was undefined. I am not sure if this is related at all, but mention it in case others are seeing it. After adding a separate patch for the type error this patch addressed the issue. Thank you!

The other error when $element[0] is empty is not directly related to this one.

I created 🐛 Javascript warning from content language and translation page Fixed for that error, and provided a fix.

this was a mistake in 📌 Refactor (if feasible) use of jquery is function to use vanillaJS Fixed , updated the code to reflect what there before

Committed 223f5c0 and pushed to 11.x. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.

@nod: This is such a heavy bug, could it please be cherry-picked into 10.2.x?

See 🐛 Content language and translation fields are hidden (display: none;) after save Active

The functionality is essentially unusable, and this is an important part of core translations.

cherry picked to 10.2.x

Thank you so much @nod! I saw you also cherry-picked 🐛 Javascript warning from content language and translation page Fixed ! Great!!
Looking forward to the next minor release to fix this.

This is a duplicate or related https://www.drupal.org/project/drupal/issues/3378812 🐛 "Content language and translation" form doesn't save "Custom language settings" data Postponed: needs info