mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-21 01:05:45 +00:00
681ee8a0d0
The gist of the problem I introduced with the framebuffer coordinate system is that we provided the window rect (effectively) twice: 1. when computing the document rectangle (and Y-inverting it) 2. when rendering If between these points the window got resized (during scene building), we end up with our document aligned to bottom left corner. The user expects content to still be aligned to the top left, so that's what is visible as a bug. The change here switched scene building to only care about device coordinate space, restraining the framebuffer coordinates to be mostly an implementation detail of the renderer/device (the way it was originally meant to be, when introduced). This way the current window size is only considered once during rendering. Differential Revision: https://phabricator.services.mozilla.com/D28731 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| common | ||
| alpha_perf.rs | ||
| animation.rs | ||
| basic.rs | ||
| blob.rs | ||
| Cargo.toml | ||
| document.rs | ||
| frame_output.rs | ||
| iframe.rs | ||
| image_resize.rs | ||
| multiwindow.rs | ||
| README.md | ||
| scrolling.rs | ||
| texture_cache_stress.rs | ||
| yuv.rs | ||
Examples
This directory contains a collection of examples which uses the WebRender API.
To run an example e.g. basic, try:
cargo run --bin basic