Deleted Element is handled incorrectly in the sample code for how-to-accept-all-revisions-in-a-word-processing-document.md
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- xml
- Domain
- documentation
Research direction
Open how-to-accept-all-revisions-in-a-word-processing-document.md and inspect the Deleted Element section and its sample code. Compare the sample's handling of w:del with the Word Accept All Changes result shown in the issue. Done means the description and sample produce the documented accepted-revision structure rather than rejecting the deletion.
Written by the indexing model from the issue text.
Description
The description in the Deleted Element section is fine. But when this element (w:del) is simply removed from the document, instead of accepting the change, the exact opposite happens - it is rejected.
Suppose we have:
<w:p w14:paraId="2E6899F7" w14:textId="72053AB6" w:rsidR="002A5A2D" w:rsidDel="005D1F29" w:rsidRDefault="001E6ED1">
<w:pPr>
<w:rPr>
<w:del w:id="0" w:author="snnz" w:date="2026-05-28T14:14:00Z" />
</w:rPr>
</w:pPr>
<w:r>
<w:t>Paragraph 1.</w:t>
</w:r>
<w:ins w:id="1" w:author="snnz" w:date="2026-05-28T14:14:00Z">
<w:r w:rsidR="005D1F29">
<w:t xml:space="preserve"> </w:t>
</w:r>
</w:ins>
</w:p>
<w:p w14:paraId="5188888E" w14:textId="7E01ACD4" w:rsidR="001E6ED1" w:rsidRDefault="001E6ED1" w:rsidP="005D1F29">
<w:r>
<w:t>Paragraph 2.</w:t>
</w:r>
</w:p>
Word's Accept All Changes command results in:
<w:p w14:paraId="5188888E" w14:textId="7170ECC0" w:rsidR="001E6ED1" w:rsidRDefault="001E6ED1" w:rsidP="005D1F29">
<w:r>
<w:t>Paragraph 1.</w:t>
</w:r>
<w:r w:rsidR="005D1F29">
<w:t xml:space="preserve"> </w:t>
</w:r>
<w:r>
<w:t>Paragraph 2.</w:t>
</w:r>
</w:p>
And the sample code produces the following:
<w:p w:rsidR="002A5A2D" w:rsidDel="005D1F29" w:rsidRDefault="001E6ED1" w14:paraId="2E6899F7" w14:textId="72053AB6">
<w:pPr>
<w:rPr />
</w:pPr>
<w:r>
<w:t>Paragraph 1.</w:t>
</w:r>
<w:r xmlns:w="http://schemas.openxmlformats.org/wordprocessingml/2006/main" w:rsidR="005D1F29">
<w:t xml:space="preserve"> </w:t>
</w:r>
</w:p>
<w:p w:rsidR="001E6ED1" w:rsidP="005D1F29" w:rsidRDefault="001E6ED1" w14:paraId="5188888E" w14:textId="7E01ACD4">
<w:r>
<w:t>Paragraph 2.</w:t>
</w:r>
</w:p>
- Dominant language
- PowerShell
- Stars
- 110
- Forks
- 73
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OfficeDev/open-xml-docs
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
OfficeDev/open-xml-docs#343 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
OfficeDev/open-xml-docs#333 ·
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
OfficeDev/open-xml-docs#173 ·
-
OfficeDev/open-xml-docs#159 · 6 comments · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
OfficeDev/open-xml-docs#153 · 1 comment ·
All issues in OfficeDev/open-xml-docs
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100