From 913d9221aa5a06f775166ed66d070d55602c768a Mon Sep 17 00:00:00 2001 From: Andreas Kling Date: Fri, 7 Oct 2022 12:47:46 +0200 Subject: [PATCH] LibWeb: Don't insert inline nodes directly under inline-flex container Yet another legacy "is inline-block?" condition was causing us to insert inline nodes directly as children of inline-flex containers (instead of wrapping them in anonymous blocks, which would then cause them to become flex items.) --- Userland/Libraries/LibWeb/Layout/TreeBuilder.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Userland/Libraries/LibWeb/Layout/TreeBuilder.cpp b/Userland/Libraries/LibWeb/Layout/TreeBuilder.cpp index 1d03275044..f04f793613 100644 --- a/Userland/Libraries/LibWeb/Layout/TreeBuilder.cpp +++ b/Userland/Libraries/LibWeb/Layout/TreeBuilder.cpp @@ -58,7 +58,7 @@ static bool has_in_flow_block_children(Layout::Node const& layout_node) static Layout::Node& insertion_parent_for_inline_node(Layout::NodeWithStyle& layout_parent) { - if (layout_parent.is_inline() && !layout_parent.is_inline_block()) + if (layout_parent.display().is_inline_outside() && layout_parent.display().is_flow_inside()) return layout_parent; if (layout_parent.display().is_flex_inside()) {