You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b7fc8c9
Browse filesBrowse the repository at this point in the historyBrowse files
Add real per-type fragment content painters (image/hr/frame/marker)
Ports PeachPDF's IFragmentContentPainter/FragmentContentPainters
architecture: a stateless painter per replaced/leaf box type, dispatched
by FragmentPainter instead of delegating into CssBox.Paint. The actual
per-pixel drawing logic stays on the CssBox subclasses (extracted from
their PaintImp bodies into internal methods PaintImp itself now also
calls, so there is exactly one implementation, not a parallel one) -
this keeps the port a faithful re-shaping rather than a rewrite.
CssBoxImage/CssBoxFrame gained an explicit EnsureImageLoadStarted/
EnsureVideoImageLoadStarted method: their lazy image-load trigger lives
in PaintImp today and is the *primary* load trigger for the common
async case (MeasureWordsSize only starts loading when
AvoidAsyncImagesLoading/AvoidImagesLateLoading is set), so the new
painters must replicate it or async images would never load.
List item markers previously painted via a direct box.ListItemBox.Paint(g)
call reading the live mutable tree; FragmentEmitter now builds a real
BoxFragment for the marker (BoxFragment.MarkerFragment, kept separate
from Children to preserve CssBox.PaintImp's paint-after-clip-pop timing,
since an outside-position marker can legitimately hang outside the
element's own overflow clip) and FragmentPainter paints it from there.
CssBox.Paint/PaintImp are NOT deleted: HtmlRenderer.PdfSharp.HtmlContainer
still exposes a public single-surface PerformPaint(XGraphics) overload
that a caller can reach directly (bypassing PdfGenerator's per-fragmentainer
loop) with a real multi-fragmentainer FragmentTree, which the fallback
`_root.Paint(g)` branch in HtmlContainerInt.PerformPaint(RGraphics) still
serves correctly. Deleting it would require new page-stacking transform
logic this session doesn't have a tested replacement for - left as a
real, live-verified deviation from the original plan's F3 assumption.
Full regression suite (35 image-diff tests) and PDF test suite (15 tests)
pass unchanged; all TFMs build clean across the whole solution.
0 commit comments