Mirrors/servo
1
0
Fork 0
mirror of https://github.com/servo/servo.git synced 2025-06-06 16:45:39 +00:00
Code Issues Projects Releases Packages Wiki Activity

script: Split style and layout data in DOM nodes (#31985)

Browse source 
This change splits the style and layout data in DOM nodes that is
populated by style and layout passes. This makes Servo's data design
more like Gecko's. This allows:

1. Removing the various `StyleAndLayout` data structures used by layout.
2. Removing the `GetStyleAndLayoutData` and
   `GetStyleAndOpaqueLayoutData` traits. Accessing style and layout data
   are now just functions on the `LayoutNode` and `ThreadSafeLayoutNode`
   traits.
3. Styling now doesn't populate layout data. This is is postponed until
   layout itself.
4. Allows the DOM wrappers to no longer have to be generic over the
   layout data. This data was already stored using `std::any::Any` and
   the new code just makes layout responsible for downcasting. Cleaning
   up the generic type parameter in the DOM wrappers can happen in a
   followup change.

The main benefit to all of this is that we should be able to remove
unsafe creation of `ServoLayoutNode` in layout and
`TrustedLayoutNodeAddress` entirely, because `ServoLayoutNode` will be
able to be passed directly from script to layout. In addition, this
removes one more abstraction layer from the layout DOM wrappers, making
the code a lot more understandable.

Note: This increases the measured size of DOM types, but the same data
is stored. It's simply that before that data was stored behind a heap
pointer.
This commit is contained in:
Martin Robinson 2024-04-04 09:56:51 +02:00 • committed by GitHub
parent 1ed6b96684
commit 08ef158d4e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
15 changed files with 230 additions and 293 deletions
Download patch file Download diff file Expand all files Collapse all files

8
components/layout/query.rs
View file

@ -40,7 +40,7 @@ use crate::flow::{Flow, GetBaseFlow};
use crate::fragment::{Fragment, FragmentBorderBoxIterator, FragmentFlags, SpecificFragmentInfo};
use crate::inline::InlineFragmentNodeFlags;
use crate::sequential;
use crate::wrapper::LayoutNodeLayoutData;
use crate::wrapper::ThreadSafeLayoutNodeHelpers;
// https://drafts.csswg.org/cssom-view/#overflow-directions
fn overflow_direction(writing_mode: &WritingMode) -> OverflowDirection {
@ -851,7 +851,7 @@ fn process_resolved_style_request_internal<'dom>(
where
N: LayoutNode<'dom>,
{
let maybe_data = layout_el.borrow_layout_data();
let maybe_data = layout_el.as_node().borrow_layout_data();
let position = maybe_data.map_or(Point2D::zero(), |data| {
match data.flow_construction_result {
ConstructionResult::Flow(ref flow_ref, _) => flow_ref
@ -1021,8 +1021,8 @@ fn inner_text_collection_steps<'dom>(
_ => child,
};
let element_data = match node.get_style_and_opaque_layout_data() {
Some(data) => &data.style_data.element_data,
let element_data = match node.style_data() {
Some(data) => &data.element_data,
None => continue,
};