Only fire accessible load complete events on the main frame on Android.

Only fire accessible load complete events on the main frame on Android.

BUG=604524
Committed: https://crrev.com/93972adf9120670ef5c6c42b609aeeeb4bc41ad4
Cr-Commit-Position: refs/heads/master@{#388896}

[dmazzoni, 2016-04-18 22:47:40]

Description was changed from

==========
Only fire accessible load complete events on the main frame on Android.

BUG=604524
==========

to

==========
Only fire accessible load complete events on the main frame on Android.

BUG=604524
==========

[dmazzoni, 2016-04-18 22:47:50]

dmazzoni@chromium.org changed reviewers:
+ dtseng@chromium.org

[David Tseng, 2016-04-18 23:21:56]

https://codereview.chromium.org/1894113003/diff/1/content/browser/accessibili...
File content/browser/accessibility/browser_accessibility_manager_android.cc
(left):

https://codereview.chromium.org/1894113003/diff/1/content/browser/accessibili...
content/browser/accessibility/browser_accessibility_manager_android.cc:222: //
node has changed.
Do you still need to do this?

[dmazzoni, 2016-04-19 18:52:23]

https://codereview.chromium.org/1894113003/diff/1/content/browser/accessibili...
File content/browser/accessibility/browser_accessibility_manager_android.cc
(left):

https://codereview.chromium.org/1894113003/diff/1/content/browser/accessibili...
content/browser/accessibility/browser_accessibility_manager_android.cc:222: //
node has changed.
On 2016/04/18 23:21:56, David Tseng wrote:
> Do you still need to do this?

Yes, Peter says it's definitely needed for BrailleBack, because it could
possibly affect the content of the current braille line.

[David Tseng, 2016-04-19 20:36:30]

https://codereview.chromium.org/1894113003/diff/1/content/browser/accessibili...
File content/browser/accessibility/browser_accessibility_manager_android.cc
(left):

https://codereview.chromium.org/1894113003/diff/1/content/browser/accessibili...
content/browser/accessibility/browser_accessibility_manager_android.cc:222: //
node has changed.
On 2016/04/19 18:52:23, dmazzoni wrote:
> On 2016/04/18 23:21:56, David Tseng wrote:
> > Do you still need to do this?
> 
> Yes, Peter says it's definitely needed for BrailleBack, because it could
> possibly affect the content of the current braille line.

I wasn't clear, sorry: in the case of a load complete on a frame, do you need to
do this?

[dmazzoni, 2016-04-21 17:46:28]

On 2016/04/19 20:36:30, David Tseng wrote:
> I wasn't clear, sorry: in the case of a load complete on a frame, do you need
to
> do this?

Oh! Good idea. To be safe I moved it after the handleContentChanged. I think
load complete events were usually redundant and the tree already should have
changed, but this is definitely safer.

[David Tseng, 2016-04-21 20:29:55]

lgtm

[dmazzoni, 2016-04-21 20:44:57]

The CQ bit was checked by dmazzoni@chromium.org

[commit-bot: I haz the power, 2016-04-21 20:45:24]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1894113003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1894113003/20001

[commit-bot: I haz the power, 2016-04-21 21:04:41]

Description was changed from

==========
Only fire accessible load complete events on the main frame on Android.

BUG=604524
==========

to

==========
Only fire accessible load complete events on the main frame on Android.

BUG=604524
==========

[commit-bot: I haz the power, 2016-04-21 21:04:42]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-04-22 19:39:22]

Description was changed from

==========
Only fire accessible load complete events on the main frame on Android.

BUG=604524
==========

to

==========
Only fire accessible load complete events on the main frame on Android.

BUG=604524

Committed: https://crrev.com/93972adf9120670ef5c6c42b609aeeeb4bc41ad4
Cr-Commit-Position: refs/heads/master@{#388896}
==========

[commit-bot: I haz the power, 2016-04-22 19:39:23]

Patchset 2 (id:??) landed as
https://crrev.com/93972adf9120670ef5c6c42b609aeeeb4bc41ad4
Cr-Commit-Position: refs/heads/master@{#388896}