mirror of
https://github.com/servo/servo.git
synced 2025-09-27 07:10:19 +01:00
d29ad5b9c3
In the past, all scroll offsets were reset when navigating between pages, and layouts probably didn't preserve their scroll positions between back and forward operations. Whatever the reason, the compositor was still trying to reset these positions right after a load. This is an issue, because a page can request a scroll during a load, and this scroll might be requested from `<iframe>` content. In that case, the scroll positions should be the ones that layout reflects and not cleared from the Compositor. This reset operation had the potential to stomp on scroll positions set during load. It's quite likely that the Compositor shouldn't be trying to reset them at all, so just stop doing that. This removes a source of intermittency when running tests that set scroll positions. Testing: Once #39475 lands after this, its test should always pass. Signed-off-by: Oriol Brufau <obrufau@igalia.com> |
||
|---|---|---|
| .. | ||
| Cargo.toml | ||
| compositor.rs | ||
| lib.rs | ||
| refresh_driver.rs | ||
| touch.rs | ||
| tracing.rs | ||
| webview_manager.rs | ||
| webview_renderer.rs | ||