CMS Article Body not rendering/saving UL/OL lists

Hi!

I’m creating/updating CMS Items programmatically using the Webflow Node SDK.

Everything works as expected, except for that Webflow is omitting any HTML Lists (<ol> AND <ul>) when the html gets sent via the API.

For example:

If I send the following to the API:

{
  "article-body": `<h3 id="transform">Transform</h3>
<p>The <em>Transform</em> property is used to control the size and positioning of the group. It is expressed as percentages of the canvas, and the Lock icon between the width (W) and height (H) inputs allows you to fix the current aspect ratio.</p>
<ul>
<li><strong>X</strong>: The <em>X</em> position of the center point in relation to the Canvas width (i.e. 0% aligns group center left, 100% aligns group center right)</li>
<li><strong>Y</strong>: The <em>Y</em> position of the center point in relation to the Canvas height (i.e. 0% aligns group center top, 100% aligns group center bottom)</li>
<li><strong>W</strong>: The <em>W</em> width in relation to the Canvas width.</li>
<li><strong>H</strong>: The <em>H</em> height in relation to the Canvas height.</li>
</ul>
<h2 id="conclusion">Conclusion</h2>
<p>I conclude.</p>`
}

The following renders in the CMS:

I also inspected the HTML in the editor, and it’s not a styling issue. The original gets saved as a list of linebreaks, like the following:

<ol data-w-id="dd740868-e96d-b346-fb75-792784def9c9" data-wf-id="[&quot;dd740868-e96d-b346-fb75-792784def9c9&quot;]" data-automation-id="dyn-item-article-body-input" role="list"><br data-w-id="LineBreak" data-wf-id="[&quot;LineBreak&quot;]" data-automation-id="dyn-item-article-body-input"><br data-w-id="LineBreak" data-wf-id="[&quot;LineBreak&quot;]" data-automation-id="dyn-item-article-body-input"><br data-w-id="LineBreak" data-wf-id="[&quot;LineBreak&quot;]" data-automation-id="dyn-item-article-body-input"><br data-w-id="LineBreak" data-wf-id="[&quot;LineBreak&quot;]" data-automation-id="dyn-item-article-body-input"><br data-w-id="LineBreak" data-wf-id="[&quot;LineBreak&quot;]" data-automation-id="dyn-item-article-body-input"><br data-w-id="LineBreak" data-wf-id="[&quot;LineBreak&quot;]" data-automation-id="dyn-item-article-body-input"><br data-w-id="LineBreak" data-wf-id="[&quot;LineBreak&quot;]" data-automation-id="dyn-item-article-body-input"><br data-w-id="LineBreak" data-wf-id="[&quot;LineBreak&quot;]" data-automation-id="dyn-item-article-body-input"><br data-w-id="LineBreak" data-wf-id="[&quot;LineBreak&quot;]" data-automation-id="dyn-item-article-body-input"><br data-w-id="LineBreak" data-wf-id="[&quot;LineBreak&quot;]" data-automation-id="dyn-item-article-body-input"></ol>

I am also having this issue when importing CMS content via the API. In my case, thankfully, the content does render on the published page.

I’ve submitted a support ticket but it seems like this might be a known, long-standing, bug?