@mudasirweb As @christosgeorgiadis suggested the work for fixing this issue is already started in the related issue 3493765. I think we need to close this issue and continue from there.
The related issue (3495320) fixes this issue.
A lot of people are saying patch from 17 works and different people have commited changes as patches and the merge request. Which one will be merged? Can one of the module maintainers merge this and make a new release?
We encounter the same issue where untranslatable paragraph fields, such as a field for classes (e.g., m-auto being translated to m-car), are being translated. We use a paragraph called "Settings," which includes several fields for enhancing a parent paragraph by adding classes or animations. This "Settings" paragraph is linked to all other paragraphs via an Entity Reference Revisions field and does not require translation.
The content translation is disabled for the "Settings" paragraph, but this causes it to not function as expected: the fields are being translated. When we enable content translation, the untranslatable fields are no longer translated, and everything works. While this solution works for now, it feels like an unintended workaround rather than the expected behavior.
The issue is fixed with the last MR changes from VladimirAus.
saschaeggi → credited coretex → .
I have the same issue. The rc-9 update has an update where the toolbar libraries are loaded within the toolbar.theme. In the rc-8 the libraries are always loaded (in the page.theme) even on the login screen. One of the dependencies of the toolbar is the core/once library. In rc-9 the toolbar is not loaded on the user login and the core/once is needed with the gin_accent library but is not defined as dependency. The suggested change also solves my issue.