2d0cae27cf
Currently, any layout changes applied to the PDF document (i.e. page rotation or two-up view) after the accessibility tree has loaded does not update the page bounds. Because the accessiblity tree has read-only nodes, the only way to resolve the issue is to reload all the nodes of the tree on each layout change. Note: This CL only fixes page bounds and positions. The bounds of page content such as text or annotations still do not rotate with the rest of the document. Those issues will be fixed in a follow-up. Bug: 1150665 Change-Id: I2fbf2cb26f38ee3fed076333c0b224a8ede7947e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2553217 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by: Ankit Kumar 🌪️ <ankk@microsoft.com> Reviewed-by: Raymes Khoury <raymes@chromium.org> Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Cr-Commit-Position: refs/heads/master@{#830918}
Chromium
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.
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.