Repository navigation
fix(layout): leave a section holding an object in a switch unsupported in the page estimate - #502
Conversation
airmang
left a comment
There was a problem hiding this comment.
Reviewed exact head 68bb443 and surrounding section-support/object discovery code. Reporting sections containing objects in a run-level hp:switch as unsupported is a conservative response to currently unmeasured wrapping; chart/default-OLE coverage and removal comparison exercise the boundary. No code defect found. Locally, 10 related switch/unsupported tests passed. All 13 exact-head checks pass; workflow SHA verified and CI test/lint/type/hygiene logs inspected (6,867 passed, 18 skipped, 1 xfailed).
Merge is held: after #499 and #501 merged, scratch integration against current main 97c2bef reproduces a CHANGELOG.md content conflict. Preserve both PR changelog entries when resolving against latest main, then revalidate the updated head. No conflict resolution was pushed and no integration-test pass is claimed for the conflicted tree.
…in the page estimate A chart is saved in a run's hp:switch, the OLE object standing for it in hp:default, and Hancom Office lays it out like any other object: wrapped square, it narrows the lines beside it. The page estimate looked for objects among a run's own children only and laid those lines out as if it were not there; such a section is now unsupported. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
68bb443 to
40cbc96
Compare
Summary
hp:switch, with the OLE object standing for it inhp:default. Hancom Office lays such an object out like any other: wrapped square, it narrows the lines beside it.an object in a switch (hp:switch)) rather than estimating it wrongly.Test plan
🤖 Generated with Claude Code