commit | c5edf53479716bc38603713b333e8a7468f03c76 | [log] [tgz] |
---|---|---|
author | Aaron Leventhal <aleventhal@google.com> | Tue Feb 27 19:18:46 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 27 19:18:46 2024 |
tree | 4a81afee30418f8e3d2d28ae95bd4ed40c981f4d | |
parent | 45c75eb005d2d5f78a9d8e9a4a0e021b78114ad9 [diff] |
M123: [A11y] Empty serializations are possible This check disallowing empty serializations was added in CL:5249680, but there an be times where there were updates that get rejected by the serializer because they are on now-unincluded nodes, and therefore the set of dirty objects can be empty here. The previous code was correct. (cherry picked from commit e832367febd461241666d7a00530fdbc1de5707f) Fixed: 326224601 Change-Id: I16337281cc0b23fde67ea0474f423353295e6c29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5314159 Auto-Submit: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by: David Tseng <dtseng@chromium.org> Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1263677} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5318084 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6312@{#215} Cr-Branched-From: 6711dcdae48edaf98cbc6964f90fac85b7d9986e-refs/heads/main@{#1262506}
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.