ladybird/Tests/LibWeb/Layout/expected/css-all-unset.txt

Viewport <#document> at (0,0) content-size 800x600 children: inline
  InlineNode <html>
    InlineNode <head>
      InlineNode <style>
        frag 0 from TextNode start: 1, length: 18, rect: [0,0 134.984375x17] baseline: 13.296875
            "* { all: unset; } "
        TextNode <#text>
    InlineNode <body>
      frag 0 from TextNode start: 0, length: 13, rect: [135,0 103.140625x17] baseline: 13.296875
          "Hello friends"
      TextNode <#text>

ViewportPaintable (Viewport<#document>) [0,0 800x600]
  InlinePaintable (InlineNode<HTML>)
    InlinePaintable (InlineNode<HEAD>)
      InlinePaintable (InlineNode<STYLE>)
        TextPaintable (TextNode<#text>)
    InlinePaintable (InlineNode<BODY>)
      TextPaintable (TextNode<#text>)
LibWeb: Implement the CSS `all` property This sets all longhand values to one of initial, inherit, unset or revert. Note that revert is not supported yet, but will be soon. 2023-07-29 08:53:24 +00:00			`Viewport <#document> at (0,0) content-size 800x600 children: inline`
			`InlineNode <html>`
			`InlineNode <head>`
			`InlineNode <style>`
LibWeb: Make inline paintables own their fragments The paintable tree structure more closely matches the painting order when fragments are owned by corresponding inline paintables. This change does not affect the layout tree, as it is more convenient for layout purposes to have all fragments owned by a block container in one place. Additionally, this improves performance significantly on pages with many fragments, as we no longer have to walk the ancestor chain up to the closest block container to determine if a fragment belongs to an inline paintable. 2024-01-13 12:11:31 +00:00			`frag 0 from TextNode start: 1, length: 18, rect: [0,0 134.984375x17] baseline: 13.296875`
			`"* { all: unset; } "`
LibWeb: Implement the CSS `all` property This sets all longhand values to one of initial, inherit, unset or revert. Note that revert is not supported yet, but will be soon. 2023-07-29 08:53:24 +00:00			`TextNode <#text>`
			`InlineNode <body>`
LibWeb: Make inline paintables own their fragments The paintable tree structure more closely matches the painting order when fragments are owned by corresponding inline paintables. This change does not affect the layout tree, as it is more convenient for layout purposes to have all fragments owned by a block container in one place. Additionally, this improves performance significantly on pages with many fragments, as we no longer have to walk the ancestor chain up to the closest block container to determine if a fragment belongs to an inline paintable. 2024-01-13 12:11:31 +00:00			`frag 0 from TextNode start: 0, length: 13, rect: [135,0 103.140625x17] baseline: 13.296875`
			`"Hello friends"`
LibWeb: Implement the CSS `all` property This sets all longhand values to one of initial, inherit, unset or revert. Note that revert is not supported yet, but will be soon. 2023-07-29 08:53:24 +00:00			`TextNode <#text>`
LibWeb+headless-browser: Include paint tree in layout test output This will give us a more comprehensive look at what actually gets rendered in the end, and also allows us to catch more behavior changes. 2023-08-03 07:59:12 +00:00
LibWeb: Add ViewportPaintable to represent viewports in the paint tree This patch just adds the new root paintable and updates the tests expectations. The next patch will move painting logic from the layout viewport to the paint viewport. 2023-08-18 13:52:40 +00:00			`ViewportPaintable (Viewport<#document>) [0,0 800x600]`
LibWeb+headless-browser: Include paint tree in layout test output This will give us a more comprehensive look at what actually gets rendered in the end, and also allows us to catch more behavior changes. 2023-08-03 07:59:12 +00:00			`InlinePaintable (InlineNode<HTML>)`
			`InlinePaintable (InlineNode<HEAD>)`
			`InlinePaintable (InlineNode<STYLE>)`
			`TextPaintable (TextNode<#text>)`
			`InlinePaintable (InlineNode<BODY>)`
			`TextPaintable (TextNode<#text>)`