Repository navigation
Commit 3dff788
committed
Document that list markers survive container relocation without help
A third audit pass raised a plausible concern: does PropagateContainerRelocation's
raw Location reassignment leave a list-item's marker stale, the way it would
without CssBox.OffsetTop's explicit marker handling? Investigated empirically
with a diagnostic test (with and without an explicit marker shift) - no
difference. CreateListItemBox recomputes the marker's position from its
owner's current Location unconditionally on every PerformLayoutImp call, and
every ancestor this method climbs is still mid-PerformLayoutImp when it
runs, so the marker always re-derives correctly afterward. Recorded as an
investigated non-issue rather than adding redundant handling.1 parent 2015821 commit 3dff788
1 file changed
Lines changed: 12 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
294 | 294 | | |
295 | 295 | | |
296 | 296 | | |
| 297 | + | |
| 298 | + | |
| 299 | + | |
| 300 | + | |
| 301 | + | |
| 302 | + | |
| 303 | + | |
| 304 | + | |
| 305 | + | |
| 306 | + | |
| 307 | + | |
| 308 | + | |
297 | 309 | | |
298 | 310 | | |
299 | 311 | | |
| |||
0 commit comments