Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2026-04-20 02:40:27 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Tests/LibWeb/Layout/expected/css-counters/counters-function.txt

318 lines
20 KiB
Text
Raw Normal View History

LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
Viewport <#document> at [0,0] [0+0+0 800 0+0+0] [0+0+0 600 0+0+0] children: not-inline
BlockContainer <html> at [0,0] [0+0+0 800 0+0+0] [0+0+0 286 0+0+0] [BFC] children: not-inline
BlockContainer <body> at [8,8] [8+0+0 784 0+0+8] [8+0+0 270 0+0+8] children: not-inline
BlockContainer <div.ol> at [24,8] [0+0+16 768 0+0+0] [0+0+0 270 0+0+0] children: not-inline
BlockContainer <(anonymous)> at [24,8] [0+0+0 768 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [24,8] [0+0+0 768 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [42.125,8 14.265625x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"A"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [24,8] [0+0+0 18.125 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [24,8 6.34375x18] baseline: 13.796875
"1"
frag 1 from TextNode start: 0, length: 2, rect: [30.34375,8 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [24,26] [0+0+0 768 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [24,26] [0+0+0 768 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [44.59375,26 9.34375x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"B"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [24,26] [0+0+0 20.59375 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [24,26 8.8125x18] baseline: 13.796875
"2"
frag 1 from TextNode start: 0, length: 2, rect: [32.8125,26 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [24,44] [0+0+0 768 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [24,44] [0+0+0 768 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [44.875,44 10.3125x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"C"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [24,44] [0+0+0 20.875 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [24,44 9.09375x18] baseline: 13.796875
"3"
frag 1 from TextNode start: 0, length: 2, rect: [33.09375,44 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [24,62] [0+0+0 768 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [24,62] [0+0+0 768 0+0+0] [0+0+0 162 0+0+0] children: not-inline
BlockContainer <(anonymous)> at [24,62] [0+0+0 768 0+0+0] [0+0+0 18 0+0+0] children: inline
InlineNode <(anonymous)> at [24,62] [0+0+0 11.53125 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [24,62 7.75x18] baseline: 13.796875
"4"
frag 1 from TextNode start: 0, length: 1, rect: [31.75,62 3.78125x18] baseline: 13.796875
":"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <div.ol> at [40,80] [0+0+16 752 0+0+0] [0+0+0 144 0+0+0] children: not-inline
BlockContainer <(anonymous)> at [40,80] [0+0+0 752 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [40,80] [0+0+0 752 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [70.21875,80 11.140625x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"D"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [40,80] [0+0+0 30.21875 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 3, rect: [40,80 18.4375x18] baseline: 13.796875
"4.1"
frag 1 from TextNode start: 0, length: 2, rect: [58.4375,80 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [40,98] [0+0+0 752 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [40,98] [0+0+0 752 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [72.6875,98 11.859375x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"E"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [40,98] [0+0+0 32.6875 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 3, rect: [40,98 20.90625x18] baseline: 13.796875
"4.2"
frag 1 from TextNode start: 0, length: 2, rect: [60.90625,98 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [40,116] [0+0+0 752 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [40,116] [0+0+0 752 0+0+0] [0+0+0 72 0+0+0] children: not-inline
BlockContainer <(anonymous)> at [40,116] [0+0+0 752 0+0+0] [0+0+0 18 0+0+0] children: inline
InlineNode <(anonymous)> at [40,116] [0+0+0 24.96875 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 3, rect: [40,116 21.1875x18] baseline: 13.796875
"4.3"
frag 1 from TextNode start: 0, length: 1, rect: [61.1875,116 3.78125x18] baseline: 13.796875
":"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <div.ol> at [56,134] [0+0+16 736 0+0+0] [0+0+0 54 0+0+0] children: not-inline
BlockContainer <(anonymous)> at [56,134] [0+0+0 736 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [56,134] [0+0+0 736 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [99.65625,134 12.546875x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"F"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [56,134] [0+0+0 43.65625 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 5, rect: [56,134 31.875x18] baseline: 13.796875
"4.3.1"
frag 1 from TextNode start: 0, length: 2, rect: [87.875,134 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [56,152] [0+0+0 736 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [56,152] [0+0+0 736 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [102.125,152 13.234375x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"G"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [56,152] [0+0+0 46.125 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 5, rect: [56,152 34.34375x18] baseline: 13.796875
"4.3.2"
frag 1 from TextNode start: 0, length: 2, rect: [90.34375,152 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [56,170] [0+0+0 736 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [56,170] [0+0+0 736 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [102.40625,170 12.234375x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"H"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [56,170] [0+0+0 46.40625 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 5, rect: [56,170 34.625x18] baseline: 13.796875
"4.3.3"
frag 1 from TextNode start: 0, length: 2, rect: [90.625,170 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [56,188] [0+0+0 736 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [40,188] [0+0+0 752 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [40,188] [0+0+0 752 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [40,188] [0+0+0 752 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [71.625,188 4.59375x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"I"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [40,188] [0+0+0 31.625 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 3, rect: [40,188 19.84375x18] baseline: 13.796875
"4.4"
frag 1 from TextNode start: 0, length: 2, rect: [59.84375,188 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [40,206] [0+0+0 752 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [40,206] [0+0+0 752 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [72.328125,206 8.90625x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"J"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [40,206] [0+0+0 32.328125 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 3, rect: [40,206 20.546875x18] baseline: 13.796875
"4.5"
frag 1 from TextNode start: 0, length: 2, rect: [60.546875,206 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [40,224] [0+0+0 752 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [24,224] [0+0+0 768 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [24,224] [0+0+0 768 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [24,224] [0+0+0 768 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [44.234375,224 9.8125x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"K"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [24,224] [0+0+0 20.234375 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [24,224 8.453125x18] baseline: 13.796875
"5"
frag 1 from TextNode start: 0, length: 2, rect: [32.453125,224 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [24,242] [0+0+0 768 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [24,242] [0+0+0 768 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [44.515625,242 10.859375x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"L"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [24,242] [0+0+0 20.515625 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [24,242 8.734375x18] baseline: 13.796875
"6"
frag 1 from TextNode start: 0, length: 2, rect: [32.734375,242 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [24,260] [0+0+0 768 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <div.li> at [24,260] [0+0+0 768 0+0+0] [0+0+0 18 0+0+0] children: inline
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [44.5,260 11.765625x18] baseline: 13.796875
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
"M"
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
InlineNode <(anonymous)> at [24,260] [0+0+0 20.5 0+0+0] [0+0+0 18 0+0+0]
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
frag 0 from TextNode start: 0, length: 1, rect: [24,260 8.71875x18] baseline: 13.796875
"7"
frag 1 from TextNode start: 0, length: 2, rect: [32.71875,260 11.78125x18] baseline: 13.796875
": "
LibWeb: Show inline positioning in layout tree dump Inline nodes in our layout tree have a position, so let's show it. By centralizing the logic for this, block nodes now lose their redundant 'content-size' dump info which is already part of the box model dump.
2025-08-27 11:32:19 +02:00
TextNode <#text> (not painted)
TextNode <#text> (not painted)
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [24,278] [0+0+0 768 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
BlockContainer <(anonymous)> at [8,278] [0+0+0 784 0+0+0] [0+0+0 0 0+0+0] children: inline
TextNode <#text> (not painted)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
ViewportPaintable (Viewport<#document>) [0,0 800x600]
Meta: Add doctypes to a few more layout tests
2025-05-04 15:39:31 +02:00
PaintableWithLines (BlockContainer<HTML>) [0,0 800x286]
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer<BODY>) [8,8 784x270]
PaintableWithLines (BlockContainer<DIV>.ol) [8,8 784x270]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
PaintableWithLines (BlockContainer(anonymous)) [24,8 768x0]
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer<DIV>.li) [24,8 768x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [24,8 18.125x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [24,26 768x0]
PaintableWithLines (BlockContainer<DIV>.li) [24,26 768x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [24,26 20.59375x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [24,44 768x0]
PaintableWithLines (BlockContainer<DIV>.li) [24,44 768x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [24,44 20.875x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [24,62 768x0]
PaintableWithLines (BlockContainer<DIV>.li) [24,62 768x162]
PaintableWithLines (BlockContainer(anonymous)) [24,62 768x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [24,62 11.53125x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer<DIV>.ol) [24,80 768x144]
PaintableWithLines (BlockContainer(anonymous)) [40,80 752x0]
PaintableWithLines (BlockContainer<DIV>.li) [40,80 752x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [40,80 30.21875x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [40,98 752x0]
PaintableWithLines (BlockContainer<DIV>.li) [40,98 752x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [40,98 32.6875x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [40,116 752x0]
PaintableWithLines (BlockContainer<DIV>.li) [40,116 752x72]
PaintableWithLines (BlockContainer(anonymous)) [40,116 752x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [40,116 24.96875x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer<DIV>.ol) [40,134 752x54]
PaintableWithLines (BlockContainer(anonymous)) [56,134 736x0]
PaintableWithLines (BlockContainer<DIV>.li) [56,134 736x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [56,134 43.65625x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [56,152 736x0]
PaintableWithLines (BlockContainer<DIV>.li) [56,152 736x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [56,152 46.125x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [56,170 736x0]
PaintableWithLines (BlockContainer<DIV>.li) [56,170 736x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [56,170 46.40625x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [56,188 736x0]
PaintableWithLines (BlockContainer(anonymous)) [40,188 752x0]
PaintableWithLines (BlockContainer(anonymous)) [40,188 752x0]
PaintableWithLines (BlockContainer<DIV>.li) [40,188 752x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [40,188 31.625x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [40,206 752x0]
PaintableWithLines (BlockContainer<DIV>.li) [40,206 752x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [40,206 32.328125x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [40,224 752x0]
PaintableWithLines (BlockContainer(anonymous)) [24,224 768x0]
PaintableWithLines (BlockContainer(anonymous)) [24,224 768x0]
PaintableWithLines (BlockContainer<DIV>.li) [24,224 768x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [24,224 20.234375x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [24,242 768x0]
PaintableWithLines (BlockContainer<DIV>.li) [24,242 768x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [24,242 20.515625x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [24,260 768x0]
PaintableWithLines (BlockContainer<DIV>.li) [24,260 768x18]
LibWeb: Dump PaintableBox dimensions for inline layout nodes We were only dumping a PaintableBox' dimensions if its layout node was a Layout::Box as well, causing us to not dump the dimensions of paintables for inline nodes in the paintable tree.
2025-07-03 14:39:57 +02:00
PaintableWithLines (InlineNode(anonymous)) [24,260 20.5x18]
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 15:55:16 +02:00
TextPaintable (TextNode<#text>)
Last: LibWeb: Add counter() and counters() functions to content property These let you format counters' current values as strings for use in generated content.
2024-07-18 20:29:02 +01:00
TextPaintable (TextNode<#text>)
LibWeb: Scale font size by 1.15 for `line-height: normal` Browsers such as Chrome and Firefox apply an arbitrary scale to the current font size if `normal` is used for `line-height`. Firefox uses 1.2 while Chrome uses 1.15. Let's go with the latter for now, it's relatively easy to change if we ever want to go back on that decision. This also requires updating the expectations for a lot of layout tests. The upside of this is that it's a bit easier to compare our layout results to other browsers', especially Chrome.
2025-04-04 15:08:15 +02:00
PaintableWithLines (BlockContainer(anonymous)) [24,278 768x0]
PaintableWithLines (BlockContainer(anonymous)) [8,278 784x0]
test-web: Dump stacking context tree in layout test output This will allow us to test (and catch regressions in) stacking context tree construction and updates, etc.
2025-07-06 14:45:04 +02:00
SC for Viewport<#document> [0,0 800x600] [children: 1] (z-index: auto)
SC for BlockContainer<HTML> [0,0 800x286] [children: 0] (z-index: auto)
Reference in a new issue Copy permalink