Body summary translation is adding p tags in content

@davidpetit
Can you give some more steps to reproduce the issue?

• field configuration
• text to be translated etc.

@steffenr

We are just using the standard body field "Text (formatted, long, with summary)" with "Summary input" enabled.

The configuration for the translator has tag handling set for html.

An example of original summary input is:
"For more than half a century, the Limelight Gala has stood as a symbol of Piaget's artistry, blending elegant design with technical prowess"

The summary input does not contain html only the body has html. However, for the translation,

tags are added to the summary in the translated version.

That said after repeating every step, I found out why this is happening. In the reviewing page for a translation for example in this path "/admin/tmgmt/items/6" for item id 6, when I check the fields to validate them, I can see that ckeditor is added to the summary field wheras it should not be added. It is ckeditor that is adding the <p> tag.

As you can see in the screenshot attached to my comment.

I will fix this by using a hook form alter to disable ckeditor from summary fields because I do not think there is any configuration to prevent this.

That said, it would be better if it was handled properly on tmgmt_job_item_edit_form build directly in tmgmt module.

Here is how I fixed it with hook form alter for this form:

if (isset($form['review']['body']['body|0']['body|0|summary']['source']['#allowed_formats'])) {
    $form['review']['body']['body|0']['body|0|summary']['source']['#allowed_formats'] = ['plain_text'];
  }
  if (isset($form['review']['body']['body|0']['body|0|translation']['source']['#allowed_formats'])) {
    $form['review']['body']['body|0']['body|0|summary']['translation']['#allowed_formats'] = 'plain_text';
  }

This force the format to plain text on summary fields and disable ckeditor. This way, no more <p> tags added to the text for summary fields.

@davidpetit Thanks for the clarification and your approach to solve it.
I'll close the issue for now. You may open an issue in tmgmt, but it looks like this is more like a drupal core thing and the handling of text formats/ especially the summary field.