Issue Summary

• When a legacy editor page containing Action Items (task lists) is converted to the new editor, extra “empty” Action Items appear in the list.

• These blank items correspond to existing legacy tasks whose body contains only a horizontal rule (<hr />).

• During conversion, the <hr /> is extracted into a separate block, but the task wrapper is left behind and rendered as a blank Action Item in the new editor.

Steps to Reproduce

1. Start with a legacy editor page.

1. Add an Action Item list and insert a horizontal rule inside one of the tasks, so that the storage format for that task becomes:
    <ac:task> <ac:task-id>123</ac:task-id> <ac:task-status>incomplete</ac:task-status> <ac:task-body> <hr /> </ac:task-body></ac:task>
2. Add some normal tasks before and after this HR‑only task in the same <ac:task-list>.

1. Save the page in the legacy editor.

1. Convert this page to the new editor (Fabric/ADF).

1. View the checklist in the new editor.

Expected Results

• The conversion should treat a task whose body is only <hr /> as a visual divider, normalising it to a standalone <hr /> block.

• No additional / empty Action Items should appear in the converted page.

• The number of visible Action Items should match the number of “real” tasks in the legacy page (i.e. tasks with actual text content).

Actual Results

• At each position where an HR‑only task existed in legacy storage, the new editor shows:

• • a blank Action Item row (checkbox with no text), and

• • a separate horizontal rule divider.

• From the user’s perspective, conversion has “added” an extra empty Action Item between real tasks, even though they never created that item explicitly.

Technical Details / Cause

• Legacy storage on affected pages contains multiple tasks of the form:
   <ac:task> <ac:task-id>102</ac:task-id> <ac:task-status>incomplete</ac:task-status> <ac:task-body> <hr /> </ac:task-body></ac:task>
• These are genuine <ac:task> nodes whose body is only <hr />.

• During conversion, the transformer pulls the <hr /> out as its own block node (expected), but does not drop or normalise the now‑empty ac:task.

• The new editor then renders this left‑over task as an empty Action Item row, leading to the perceived “extra” items after conversion.

Workaround

Currently there is no automatic/bulk workaround in product. A workaround will be added here when available.

• Per‑page workarounds:

• • In the legacy editor, edit storage and replace each HR‑only task
     <ac:task> <ac:task-id>NNN</ac:task-id> <ac:task-status>complete|incomplete</ac:task-status> <ac:task-body> <hr /> </ac:task-body></ac:task>
    with a standalone <hr /> block at the same position:
     <hr />
    Then convert the page.

• • Or, convert the page first and then manually delete each blank Action Item row in the new editor.