Enabling content translation of Canvas pages results in an unsupported state (asymmetrical translations) by default: force the known valid state if the field is marked as translatable
Currently content translation allows to configure both inputs and component tree translation. However Canvas UI currently only supports inputs translation not different component trees. The default configuration on the content translation UI enables both, resulting in an unsupported combination.
Talking to the Canvas team the component tree part is intended to be marked translatable, so it can be supported in the future. So instead of changing the translatability of that, the UI should be modified to disallow configuring the tree to be translatable.
{width="684" height="600"}
Alternatively the column groups setting could be entirely altered out of the form and forced to the only supported combination. In that case I would alter the "Components" label to "Component inputs" or somesuch to make it clear.
An "elegant" solution to this would require https://www.drupal.org/project/drupal/issues/3606969 fixed first, but the form could be modified even assuming the variance that that leads to until it is fixed, just part of the altering would not be needed after that is fixed.
issue