[hryhoriiK97]

What/Why?

Ordered lists that reach 100. clip their markers: the column is sized for 99. and numbers are right-aligned against it, so 100. draws as 00.. Each ordered list now measures its widest marker and widens its own column to fit; markerMinWidth stays the floor, lists under 100 keep the 99. column, and nested lists move with a widened parent.

This carries @mwolson's #1005 (8407374) unchanged as the first commit, plus two follow-up commits from a local review. #1005 stays open for the discussion there; GitHub refuses maintainer pushes to that branch because the fork's parent is pingdotgg/enriched-markdown, so the follow-ups land here instead.

Closes #1003.

Follow-up commits on top of #1005

Library

• Android, both packages: the nested-item margin lives in BaseListSpan via an overridable markerExtraWidth, so there is one formula for fix(android): align mixed nested list indents with iOS #1006 to extend. ListContextManager saves and restores the widening like the rest of the list state. The column is measured by a companion function instead of a throwaway span, and the new span arguments are named at call sites.
• Android: the widening is rounded to whole pixels, so the Int leading margins and the float marker positions agree at every nesting depth with proportional fonts.
• All platforms: a task item inside a widened ordered list moves with its numbered siblings, and so do its children. The Swift package already behaved this way; Android and RN iOS left tasks on the checkbox column, which produced a notch of about 25dp in a list numbered to 1000.
• iOS: listMarkerOffset is ancestorMarkerOffset to match Android, the per-list extra stays cached on the RN context, and the Swift default column width is an extension on ListStyle instead of a static on a sibling renderer.

Tests

• Suites are named by feature: ListRenderingTest(s) on every platform, with the checkbox toggle test in TaskListInteractionTest. The RN Android package gets a test/ support package like the standalone one (render helper, AST factory, and the canvas that records drawn markers), shared by both Android packages.
• Task alignment tests assert the new behavior on Android and RN iOS.

Baselines and docs

• Android captures for ordered_list_wide_markers_test recaptured on the repo's Pixel 9 API 36 AVD, where the committed ordered-list baselines pass exact-match; the originals from fix: size ordered list markers to their widest number #1005 did not. iOS captures reproduce byte for byte on iPhone 17 / iOS 26.5 and are unchanged.
• The markerMinWidth rows in the RN and Android docs mention the widening.

Testing

• Unit: RN Android ListRenderingTest (11) and TaskListInteractionTest (2); standalone Android ListRenderingTest (8) with the full :ui suite; standalone iOS ListRenderingTests (13) with the full package suite; RN iOS ListRenderingTests (6) in the example test target. ktlint, swiftlint --strict and clang-format pass.
• Maestro, iPhone 17 / iOS 26.5: ordered_list_wide_markers_test in the RN and native iOS examples; captures byte-identical to the committed baselines.
• Maestro, Pixel 9 API 36: ordered_list_wide_markers_test captured on two consecutive builds with identical output; ordered_list_test and nested_ordered_list_test pass exact-match against their main baselines, so no code path changes for lists under 100 items on React Native and Android, and the existing ordered-list captures match main pixel for pixel.

Notes

• Standalone iOS: lists with 10 or more items get a column up to about 4.6pt wider than the old fixed 20pt, since two-digit markers overflowed it. Worth a release-note line.
• For fix(android): align mixed nested list indents with iOS #1006: shortMixedNestsKeepTheirOriginalTextIndents pins the current mixed-marker indents and needs updating when it lands. With the extra in BaseListSpan, the combined resolution described in fix: size ordered list markers to their widest number #1005 should reduce to adding fix(android): align mixed nested list indents with iOS #1006's term to that one method.
• Pre-existing and unrelated, worth separate issues: ParagraphLayoutWalkerTests.testLinesMatchTextSegments fails identically on main with Xcode 27 here, and the committed Android task_list_test baseline differs from the Pixel 9 AVD by anti-aliasing only.

PR Checklist

• Code compiles and runs on iOS
• Code compiles and runs on Android
• Updated documentation/README if applicable
• Ran example app to verify changes
• E2E tests are passing
• Required E2E tests have been added (if applicable)

🤖 Generated with Claude Code