Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reland "Reland "PDF a11y: Create the status node to notify users of P…
…DF content loading"" This is a reland of commit 86927ca In the first reland CL, some of the PDFExtensionAccessibility* tests when a transient node (i.e. the status node) already got removed from the accessibility tree before calling the new helper function, which was waiting for the node to be first added to the tree. In the second reland CL, the status node and its wrapper node don't get removed anymore (so no transient node in a PDF accessibility tree), but their attributes get reset in `PdfAccessibilityTree::UnserializeNodes()`. Then, the tree format output related to these nodes (i.e. the second and the third lines in the tree format output) is manually deleted in PDFExtensionAccessibility* tests. Original change's description: > Reland "PDF a11y: Create the status node to notify users of PDF content loading" > > This is a reland of commit 72776ff > > In the original CL, some tests failed since the new helper function > assumed that a node with the given name already existed in an a11y > tree. Instead of this assumption, updated the helper function to wait > for a node with the given name to be added to the tree and then wait > for it to be removed from the tree. This helper function has been > renamed to `WaitForTransientNodeWithName()` and added to > chrome/browser/pdf/pdf_extension_accessibility_test.cc as its use case > is applied to only some of the browser tests there. > > Original change's description: > > PDF a11y: Create the status node to notify users of PDF content loading > > > > Make the status node available regardless of the PDF OCR feature to > > notify users of PDF content loading. This status node will be added and > > become available when it starts to load PDF content into an a11y tree. > > Then, the status node will be deleted once it finishes loading the > > PDF content into the tree. > > > > Note that this status node will be kept when PDF OCR is on and PDF > > doesn't have accessible text but images without alternative text. > > > > This notification is necessary especially when users open a large PDF > > (e.g. 200 or more pages) as it takes one or more minutes to load such > > a large PDF. Without notification, users won't have any accessible > > information that helps them know what's going on after opening a PDF > > until it finishes loading the PDF content into an a11y tree. > > > > AX-Relnotes: n/a. > > Bug: 1473176 > > Change-Id: Ib51af6014ca3a195ec43eff6137eeb3bff9f41c7 > > Cq-Include-Trybots: luci.chromium.try:fuchsia-official > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4792347 > > Reviewed-by: David Tseng <dtseng@chromium.org> > > Commit-Queue: Kyungjun Lee <kyungjunlee@google.com> > > Reviewed-by: Lei Zhang <thestig@chromium.org> > > Reviewed-by: Scott Violet <sky@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#1198735} > > Bug: 1473176, 1484882 > Change-Id: Ia9f505da01f448a80cf1ed999b1c9c7bdcb63bc9 > Cq-Include-Trybots: luci.chromium.try:fuchsia-official > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4884773 > Reviewed-by: David Tseng <dtseng@chromium.org> > Reviewed-by: Scott Violet <sky@chromium.org> > Reviewed-by: Lei Zhang <thestig@chromium.org> > Commit-Queue: Kyungjun Lee <kyungjunlee@google.com> > Cr-Commit-Position: refs/heads/main@{#1204078} Bug: 1473176, 1484882 Change-Id: Ie3a2e0435640983611dce3de6e6e068efd10fd79 Cq-Include-Trybots: luci.chromium.try:fuchsia-official,linux_chromium_msan_rel_ng Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4908279 Commit-Queue: Kyungjun Lee <kyungjunlee@google.com> Reviewed-by: Lei Zhang <thestig@chromium.org> Reviewed-by: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/main@{#1215741}
- Loading branch information