commit | 3325d15446fe396b715fbedfe062e21827ea55e1 | [log] [tgz] |
---|---|---|
author | Sylvain Defresne <sdefresne@chromium.org> | Mon Apr 29 15:16:52 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 29 15:16:52 2024 |
tree | b141bacbb2afcb58174ad12e385aa47cb25b68ac | |
parent | 97f0c423a84fb26b95f070c541ecfc25ce13c0ff [diff] |
[ios] Fix scroll position when using optimised session restoration When using WKWebView's native session data, the scroll position is saved. This causes the view to be incorrectly positioned when user scroll the view, quit the app and reload it, if the native session data is used and kSmoothScrollingDefault is enabled. This was only visible with optimised session restoration since the legacy session restoration had a regression causing it to fail to load the native session data (thus hiding the regression from the fullscreen code). This CL change SessionRestorationServiceImpl to not load the native session data if kSmoothScrollingDefault is enabled, behaving in the same way as LegacySessionRestorationService (bug included). Fixing LegacySessionRestorationService to correctly load the native session would make this bug happen for all users. This is undesirable. Bug: 337816888 Fixed: 336613927 Change-Id: Ifb3f448cf30dd6f2c8044dd4cfd707a2ffec590c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5490735 Reviewed-by: Aliona Dangla <alionadangla@chromium.org> Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/main@{#1293694}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.