Problem/Motivation
During the content translation/moderation integration in 8.5.x, two messages were added as warning messages, but they are actually not *warnings* IMHO.
See the screenshots in #3002571: Multiple warning messages when having untranslatable fields for one of them, when you have untranslatable fields. That's not a bug, not something you need to do anything about, that's just how it is.
The other one is on /translate, if you have pending translation revisions then you get a warning that you're not allowed to delete them:

This is a bit more warning-ish, it's an explanation why you can't delete a translation.
Proposed resolution
I'm not sure. A green/OK message is also strange?
Maybe show some other visual hint that there are fields that can't be changed/translated?
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork drupal-3004334
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3004334-messages-about-hidden
changes, plain diff MR !3258
Comments
Comment #2
berdirComment #6
hudriI'm in favor of completely removing those messages. This message has no purpose, it is just stating a fact that is already more than just obvious - guess what, the field is not on screen, so you can't edit it ;-)
Hiding non-translatable is not default and was an intentional choice of the site builder. It was either a safety measure to prevent accidental translation, or a simple "reduce clutter" intension. But in both cases and this message is unwanted and does not help at all.
Comment #8
hudriHere is a simple patch that removes the "untranslatable fields hidden" message.
Comment #9
hudriComment #11
hudriRemoved functional test and kernel test regarding the warning message
Comment #12
hudriComment #19
hudriHere is a stale patchfile of the latest merge request, updated for drupal/core:^10
This patch file completely removes the warning message again.
Comment #21
hudriStale patch file for tagged stable release v10.1.0 and for 11.x dev branch
Comment #22
smustgrave commentedIssue summary needs updating as it was written for D8. And proposed solution wasn't finalized.