Description

Editing a Single-Line Text or Multi-Line Text field in the Experience Editor might get the text wrapped in HTML <p> elements on the first saving:

<p>Text</p>

Re-editing this field does not result in adding the tag.

Solution

To resolve the issue, consider the following options:

• Upgrade Sitecore XP instance to Sitecore XP 10.1.0 or later.
• For Sitecore XP 9.3, download and install the corresponding cumulative hotfix available in KB1001332.

Alternatively, you can consider the following options:

• Remove <p> tags from the field and save changes.
• Set the HtmlEditor.LineBreak setting value to br by creating a configuration patch file in the \App_Config\Include\zzz folder.
• Make changes in the sitecore/shell/Applications/Page Models/InlineEditingUril.js file similar to the ones shown below:
  
  1. Backup the sitecore/shell/Applications/Page Modes/InlineEditingUtil.js file.
  2. Find the following piece of code in the InlineEditingUril.js file:

     Sitecore.PageModes.InlineEditingUtil.clearNonPrintableTags(target);
     
     var newLineNode = Sitecore.WebEditSettings.newLineBreak;
     if (newLineNode.toLowerCase() == "p" || newLineNode.toLowerCase() == "div")
     {
        var selection = document.getSelection();
        var range = selection.getRangeAt(0);
     
        if (!Sitecore.PageModes.InlineEditingUtil.checkContentEditable(selection.focusNode))
       {
           return true;
        }
     
        var node = document.createElement(newLineNode);
        range.insertNode(node);
        range.collapse(true);
        node.innerHTML = "<br />";
        range.selectNodeContents(node);
     
        selection.removeAllRanges();
        selection.addRange(range);
        return true;
       }
           

  3. Wrap the code from the second step in the following if statement and save the file:

     if (selection.baseNode.getAttribute("scfieldtype") !== "single-line text" && selection.baseNode.getAttribute("scfieldtype") !== "multi-line text" )
     {
     //piece of code from the second step
     }

  4. Clear the browser's cache.