These sources describe the structural and functional relationship between the layout tree and the fragment tree within Chromium's Blink engine. At the heart of this system is the LayoutView, which serves as the layout tree’s root while indirectly anchoring the fragment tree through inherited storage mechanisms. Rather than maintaining a separate global tree, each LayoutBox caches its geometric results as PhysicalFragments, which then link to one another to form a physical hierarchy used for painting and hit-testing. The texts clarify that while the LayoutView and the root fragment often correspond to the same conceptual block, they are not isomorphic due to fragmentation, where a single layout object may produce multiple fragments. Crucially, the documentation highlights how Oilpan garbage collection manages the lifetimes of these objects, ensuring that fragments can persist even if their originating layout objects are destroyed. Ultimately, the materials explain that the fragment tree represents a distinct geometry-based output that diverges from the structural layout tree to handle complex scenarios like printing and multi-column layouts.