Revert "Notify BrowserAccessibilityManager via WebContentsObserver"
This reverts commit 0885c956. Reason for revert: Unfortunately, this change results in the notification of page-load-complete happening much later than it did previously. Since a11y events aren't fired when |user_is_navigating_away_|, the result is that some events that occur early in a page's lifetime are not emitted. This is most visible for programmatic 'focus' changes; if they're not emitted, any connected AT doesn't know the focus has changed. Original change's description: > Notify BrowserAccessibilityManager via WebContentsObserver > > This is the last of a series of CLs that remove manual notifications > BrowserAccessibilityManager, now that it implements WebContentsObserver. > This CL removes manual BAM::Navigation{Succeeded,Failed} notifications > in favor of WCO::DidFinishNavigation, and BAM::UserIsNavigatingAway in > favor of WCO::DidStartLoading. > > Bug: 981271 > Change-Id: Ieca6ce0b97f2a0267fd7f2582ab1e333deb11b95 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1938489 > Reviewed-by: Matt Falkenhagen <falken@chromium.org> > Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> > Commit-Queue: Dominic Farolino <dom@chromium.org> > Cr-Commit-Position: refs/heads/master@{#720102} TBR=falken@chromium.org,dmazzoni@chromium.org,dom@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 981271 Change-Id: I41d68985b964792083aa5b6628bb3bc0972c9790 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2024154Reviewed-by:Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Ian Prest <iapres@microsoft.com> Commit-Queue: Ian Prest <iapres@microsoft.com> Cr-Commit-Position: refs/heads/master@{#735980}
Showing
Please register or sign in to comment