mirror of
https://github.com/servo/servo.git
synced 2025-08-05 05:30:08 +01:00
ad53e95080
I've done a bit of job to get this done. Right now readback is still used, but we have a `LayerId` -> `CanvasRenderer` map on the paint task, that we can use to get rid of that. I'd want review, to see if this is a good approach (I know it's not the initial `CanvasId` -> renderer approach, but it's pretty similar, since a canvas involves a `PaintLayer`). I had to do a bit of refactoring to avoid cyclic dependencies between canvas and gfx. I'd want you to review them too. It's mergeable and doesn't break any tests :P Some of my main concerns: * Does the canvas render really need to be behind an `Arc<Mutex<T>>`? * I can't clone a `NativeSurface` right now (that's why the `SendNativeSurface()` msg is unimplemented in the WebGL task). It should be easy to add that to rust-layers, supposing the caller is responsible to mark it as non-leaking, any reason to not do it? cc @jdm @pcwalton <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/6083) <!-- Reviewable:end --> |
||
|---|---|---|
| .. | ||
| css | ||
| animation.rs | ||
| block.rs | ||
| Cargo.toml | ||
| construct.rs | ||
| context.rs | ||
| data.rs | ||
| display_list_builder.rs | ||
| floats.rs | ||
| flow.rs | ||
| flow_list.rs | ||
| flow_ref.rs | ||
| fragment.rs | ||
| generated_content.rs | ||
| incremental.rs | ||
| inline.rs | ||
| layout_debug.rs | ||
| layout_task.rs | ||
| lib.rs | ||
| list_item.rs | ||
| model.rs | ||
| multicol.rs | ||
| opaque_node.rs | ||
| parallel.rs | ||
| sequential.rs | ||
| table.rs | ||
| table_caption.rs | ||
| table_cell.rs | ||
| table_colgroup.rs | ||
| table_row.rs | ||
| table_rowgroup.rs | ||
| table_wrapper.rs | ||
| text.rs | ||
| traversal.rs | ||
| wrapper.rs | ||
