Jelle Raaijmakers 9e9db9a9dd LibWeb: Store correct text offsets in PaintableFragment ... Previously, we were collapsing whitespace in Layout::TextNode and then passed the resulting string for further processing through ChunkIterator -> InlineLevelIterator -> InlineFormattingContext -> LineBuilder -> LineBoxFragment -> PaintableFragment. Our painting tree is where we deal with things like range offsets into the underlying text nodes, but since we modified the original string, the offsets were wrong. This changes the way we generate fragments: * Layout::TextNode no longer collapses whitespace as part of its stored "text for rendering", but moves this logic to ChunkIterator which splits up this text into separate views whenever whitespace needs to be collapsed. * Layout::LineBox now only extends the last fragment if its end offset is equal to the new fragment's start offset. Otherwise, there's a gap caused by collapsing whitespace and we need to generate a separate fragment for that in order to have a correct start offset. Some tests need new baselines because of the fixed start offsets. Fixes #566.		2025-09-12 15:34:09 -04:00
..
data	LibWeb: Assign linked style sheet location when parsing it	2025-04-15 09:40:38 +01:00
expected	LibWeb: Store correct text offsets in PaintableFragment	2025-09-12 15:34:09 -04:00
input	LibWeb: Propagate border-box dimensions when getting max content width	2025-09-10 11:41:30 +02:00