ladybird/Tests/LibWeb/Text/expected/hit_testing/block-element-inside-inline-element.txt

<#text>
index: 1
<BODY>
---
<#text>
index: 1
<B id="b1">
---
<#text>
index: 1
<DIV id="d1">
---
<#text>
index: 3
<B id="b1">
---
LibWeb: Change `printElement()` to not output unnecessary space No functional changes. 2025-01-25 13:40:06 +01:00			`<#text>`
LibWeb: Support inserting non-inline elements into inline elements Our layout tree requires that all containers either have inline or non-inline children. In order to support the layout of non-inline elements inside inline elements, we need to do a bit of tree restructuring. It effectively simulates temporarily closing all inline nodes, appending the block element, and resumes appending to the last open inline node. The acid1.txt expectation needed to be updated to reflect the fact that we now hoist its <p> elements out of the inline <form> they were in. Visually, the before and after situations for acid1.html are identical. 2025-01-15 16:37:30 +01:00			`index: 1`
LibWeb: Change `printElement()` to not output unnecessary space No functional changes. 2025-01-25 13:40:06 +01:00			`<BODY>`
LibWeb: Support inserting non-inline elements into inline elements Our layout tree requires that all containers either have inline or non-inline children. In order to support the layout of non-inline elements inside inline elements, we need to do a bit of tree restructuring. It effectively simulates temporarily closing all inline nodes, appending the block element, and resumes appending to the last open inline node. The acid1.txt expectation needed to be updated to reflect the fact that we now hoist its <p> elements out of the inline <form> they were in. Visually, the before and after situations for acid1.html are identical. 2025-01-15 16:37:30 +01:00			`---`
LibWeb: Change `printElement()` to not output unnecessary space No functional changes. 2025-01-25 13:40:06 +01:00			`<#text>`
LibWeb: Support inserting non-inline elements into inline elements Our layout tree requires that all containers either have inline or non-inline children. In order to support the layout of non-inline elements inside inline elements, we need to do a bit of tree restructuring. It effectively simulates temporarily closing all inline nodes, appending the block element, and resumes appending to the last open inline node. The acid1.txt expectation needed to be updated to reflect the fact that we now hoist its <p> elements out of the inline <form> they were in. Visually, the before and after situations for acid1.html are identical. 2025-01-15 16:37:30 +01:00			`index: 1`
LibWeb: Change `printElement()` to not output unnecessary space No functional changes. 2025-01-25 13:40:06 +01:00			`<B id="b1">`
LibWeb: Support inserting non-inline elements into inline elements Our layout tree requires that all containers either have inline or non-inline children. In order to support the layout of non-inline elements inside inline elements, we need to do a bit of tree restructuring. It effectively simulates temporarily closing all inline nodes, appending the block element, and resumes appending to the last open inline node. The acid1.txt expectation needed to be updated to reflect the fact that we now hoist its <p> elements out of the inline <form> they were in. Visually, the before and after situations for acid1.html are identical. 2025-01-15 16:37:30 +01:00			`---`
LibWeb: Change `printElement()` to not output unnecessary space No functional changes. 2025-01-25 13:40:06 +01:00			`<#text>`
LibWeb: Support inserting non-inline elements into inline elements Our layout tree requires that all containers either have inline or non-inline children. In order to support the layout of non-inline elements inside inline elements, we need to do a bit of tree restructuring. It effectively simulates temporarily closing all inline nodes, appending the block element, and resumes appending to the last open inline node. The acid1.txt expectation needed to be updated to reflect the fact that we now hoist its <p> elements out of the inline <form> they were in. Visually, the before and after situations for acid1.html are identical. 2025-01-15 16:37:30 +01:00			`index: 1`
LibWeb: Change `printElement()` to not output unnecessary space No functional changes. 2025-01-25 13:40:06 +01:00			`<DIV id="d1">`
LibWeb: Support inserting non-inline elements into inline elements Our layout tree requires that all containers either have inline or non-inline children. In order to support the layout of non-inline elements inside inline elements, we need to do a bit of tree restructuring. It effectively simulates temporarily closing all inline nodes, appending the block element, and resumes appending to the last open inline node. The acid1.txt expectation needed to be updated to reflect the fact that we now hoist its <p> elements out of the inline <form> they were in. Visually, the before and after situations for acid1.html are identical. 2025-01-15 16:37:30 +01:00			`---`
LibWeb: Change `printElement()` to not output unnecessary space No functional changes. 2025-01-25 13:40:06 +01:00			`<#text>`
LibWeb: Support inserting non-inline elements into inline elements Our layout tree requires that all containers either have inline or non-inline children. In order to support the layout of non-inline elements inside inline elements, we need to do a bit of tree restructuring. It effectively simulates temporarily closing all inline nodes, appending the block element, and resumes appending to the last open inline node. The acid1.txt expectation needed to be updated to reflect the fact that we now hoist its <p> elements out of the inline <form> they were in. Visually, the before and after situations for acid1.html are identical. 2025-01-15 16:37:30 +01:00			`index: 3`
LibWeb: Change `printElement()` to not output unnecessary space No functional changes. 2025-01-25 13:40:06 +01:00			`<B id="b1">`
LibWeb: Support inserting non-inline elements into inline elements Our layout tree requires that all containers either have inline or non-inline children. In order to support the layout of non-inline elements inside inline elements, we need to do a bit of tree restructuring. It effectively simulates temporarily closing all inline nodes, appending the block element, and resumes appending to the last open inline node. The acid1.txt expectation needed to be updated to reflect the fact that we now hoist its <p> elements out of the inline <form> they were in. Visually, the before and after situations for acid1.html are identical. 2025-01-15 16:37:30 +01:00			`---`