commit | 3bcf8d7222dd8c8822840795d14da3d8fba23cff | [log] [tgz] |
---|---|---|
author | Aaron Leventhal <aleventhal@google.com> | Wed Sep 21 22:21:48 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 21 22:21:48 2022 |
tree | 27bd0a9df448514053bddd7e3a5c7d33196415fd | |
parent | e3d880668f4f83d7fc9c57ec9060245ff0f37936 [diff] |
Only use document-scoped layout updates before serialization This is a precursor for work to move a11y to RunPostLifecycleSteps() in CL:3861311. There is no need to force a layout on every dirty node -- WebAXObject::MaybeUpdateLayoutAndCheckValidity() does not do this currently. The only reason to ever do this might be if we wanted updated layout information for every content-visibility: auto object, but this is not necessary because the a11y code already special cases content-visibility: auto objects with stale layout by not exposing information that requires a layout object such as style, location and perfect whitespace computation. If a user tries to navigate to one of these objects (e.g. via a skip to next heading command), then it will be scrolled into view and receive full layout at that time. In addition, forcing a layout for every content-visibility: auto node would cost performance, including for users of password managers, etc. and would ruin a lot of the benefit of content-visibility. Bug: None Change-Id: Id5ea7939bc997d0f8b100cd02fd736f3f4f9c9ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3905906 Reviewed-by: David Tseng <dtseng@chromium.org> Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/main@{#1049902}
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.