Issue metadata
Sign in to add a comment
|
Android accessibility should not handle "load complete" on iframes |
||||||||||||||||||||||
Issue descriptionTo repro: 1. Turn on TalkBack 2. Open Chrome and load CNN.com 3. The main page is supposed to focus when it finishes loading. Instead it focuses a dozen times, one for each iframe that loads. If you have haptic feedback enabled you'll feel it bump a bunch of times, it's very distracting. Issue: On Android we handle the "Load complete" event in a particular way that's intended for the main frame. We shouldn't handle the main frame that way. Visiting cnn.com generates a bunch of load complete events.
,
Apr 21 2016
,
Apr 21 2016
Your change meets the bar and is auto-approved for M51 (branch: 2704)
,
Apr 26 2016
Issue still repro on latest M51 - 51.0.2704.28. Moto g 2nd ganeration /6.0 , Nexus 5 / MOB30I
,
Apr 28 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7ac6c714fe963c31fcc81a9ec60822741efd6b3a commit 7ac6c714fe963c31fcc81a9ec60822741efd6b3a Author: Dominic Mazzoni <dmazzoni@chromium.org> Date: Thu Apr 28 22:53:07 2016 Merge to M51: Only fire accessible load complete events on the main frame on Android. BUG= 604524 Review URL: https://codereview.chromium.org/1894113003 Cr-Commit-Position: refs/heads/master@{#388896} (cherry picked from commit 93972adf9120670ef5c6c42b609aeeeb4bc41ad4) Review URL: https://codereview.chromium.org/1927953003 . Cr-Commit-Position: refs/branch-heads/2704@{#296} Cr-Branched-From: 6e53600def8f60d8c632fadc70d7c1939ccea347-refs/heads/master@{#386251} [modify] https://crrev.com/7ac6c714fe963c31fcc81a9ec60822741efd6b3a/content/browser/accessibility/browser_accessibility_manager_android.cc
,
Apr 29 2016
,
May 4 2016
Issue does not repro on latest build M51 - 51.0.2704.36 . Hence closing this issue. Thanks |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bugdroid1@chromium.org
, Apr 21 2016