mirror of
https://github.com/servo/servo.git
synced 2025-06-06 16:45:39 +00:00
e81951a973
There were two kinds of layout tracing controlled by the same debugging option: - modern layout: Functionality that dumped a JSON serialization of the layout tree before and after layout. - legacy layout: A scope based tracing that reported the process of layout in a structured way. I don't think anyone working on layout is using either of these two features. For modern layout requiring data structure to implement `serde` serialization is incredibly inconvenient and also generates a lot of extra code. We also have a more modern tracing functionality based on perfetto that we have started to use for layout and IMO it's actually being used and more robust. Signed-off-by: Martin Robinson <mrobinson@igalia.com>
47 lines
1,007 B
Rust
47 lines
1,007 B
Rust
/* This Source Code Form is subject to the terms of the Mozilla Public
|
|
* License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
* file, You can obtain one at https://mozilla.org/MPL/2.0/. */
|
|
|
|
#![deny(unsafe_code)]
|
|
|
|
mod block;
|
|
pub mod construct;
|
|
pub mod context;
|
|
pub mod data;
|
|
pub mod display_list;
|
|
mod flex;
|
|
mod floats;
|
|
pub mod flow;
|
|
mod flow_list;
|
|
pub mod flow_ref;
|
|
mod fragment;
|
|
mod generated_content;
|
|
pub mod incremental;
|
|
mod inline;
|
|
mod linked_list;
|
|
mod list_item;
|
|
mod model;
|
|
mod multicol;
|
|
pub mod parallel;
|
|
mod persistent_list;
|
|
pub mod query;
|
|
pub mod sequential;
|
|
mod table;
|
|
mod table_caption;
|
|
mod table_cell;
|
|
mod table_colgroup;
|
|
mod table_row;
|
|
mod table_rowgroup;
|
|
mod table_wrapper;
|
|
mod text;
|
|
mod text_run;
|
|
pub mod traversal;
|
|
pub mod wrapper;
|
|
|
|
// For unit tests:
|
|
// We can't use servo_arc for everything in layout, because the Flow stuff uses
|
|
// weak references.
|
|
use servo_arc::Arc as ServoArc;
|
|
|
|
pub use self::data::LayoutData;
|
|
pub use crate::fragment::{Fragment, SpecificFragmentInfo};
|