Fix reset and focus issues in OOBE

Fix reset and focus issues in OOBE

- if an extension is toggled off then on, and re-requests the desktop automation tree, it might receive tree data for a child tree before the child tree's accessibility data is reset via
chrome.automation.enableFrame.
This results in the client extension tree having an embeddedObject node with one child with role unknown.
Fix this by always resetting a child tree root that has unknown role

- work around webview focus issues by explicitly always checking the ancestors we've crossed into and always focusing first embeddedObject nodes. This should be removed once webview handles propagating upwards focus from descendants correctly.

BUG=660390
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Committed: https://crrev.com/20d6d96d1e472287cb4270b1d6c8b48973994fcd
Cr-Commit-Position: refs/heads/master@{#429978}

[David Tseng, 2016-11-04 15:28:58]

Description was changed from

==========
Fix reset and focus issues in OOBE

- if an extension is toggled off then on, and re-requests the desktop automation
tree, it might receive tree data for a child tree before the child tree's
accessibility data is reset via
chrome.automation.enableFrame.
This results in the client extension tree having an embeddedObject node with one
child with role unknown.
Fix this by always resetting a child tree root that has unknown role

- work around webview focus issues by explicitly always checking the ancestors
we've crossed into and always focusing first embeddedObject nodes. This should
be removed once webview handles propagating upwards focus from descendants
correctly.

BUG=
==========

to

==========
Fix reset and focus issues in OOBE

- if an extension is toggled off then on, and re-requests the desktop automation
tree, it might receive tree data for a child tree before the child tree's
accessibility data is reset via
chrome.automation.enableFrame.
This results in the client extension tree having an embeddedObject node with one
child with role unknown.
Fix this by always resetting a child tree root that has unknown role

- work around webview focus issues by explicitly always checking the ancestors
we've crossed into and always focusing first embeddedObject nodes. This should
be removed once webview handles propagating upwards focus from descendants
correctly.

BUG=
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[David Tseng, 2016-11-04 15:29:33]

Description was changed from

==========
Fix reset and focus issues in OOBE

- if an extension is toggled off then on, and re-requests the desktop automation
tree, it might receive tree data for a child tree before the child tree's
accessibility data is reset via
chrome.automation.enableFrame.
This results in the client extension tree having an embeddedObject node with one
child with role unknown.
Fix this by always resetting a child tree root that has unknown role

- work around webview focus issues by explicitly always checking the ancestors
we've crossed into and always focusing first embeddedObject nodes. This should
be removed once webview handles propagating upwards focus from descendants
correctly.

BUG=
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
Fix reset and focus issues in OOBE

- if an extension is toggled off then on, and re-requests the desktop automation
tree, it might receive tree data for a child tree before the child tree's
accessibility data is reset via
chrome.automation.enableFrame.
This results in the client extension tree having an embeddedObject node with one
child with role unknown.
Fix this by always resetting a child tree root that has unknown role

- work around webview focus issues by explicitly always checking the ancestors
we've crossed into and always focusing first embeddedObject nodes. This should
be removed once webview handles propagating upwards focus from descendants
correctly.

BUG=660390
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[David Tseng, 2016-11-04 15:29:34]

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

[dmazzoni, 2016-11-04 16:47:21]

lgtm

[David Tseng, 2016-11-04 18:16:58]

The CQ bit was checked by dtseng@chromium.org

[commit-bot: I haz the power, 2016-11-04 18:17:38]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-04 19:33:45]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-11-04 19:33:49]

Failed to apply the patch.
On branch working_branch
Your branch is up-to-date with 'origin/refs/pending/heads/master'.
nothing to commit, working tree clean

[commit-bot: I haz the power, 2016-11-04 20:00:20]

Description was changed from

==========
Fix reset and focus issues in OOBE

- if an extension is toggled off then on, and re-requests the desktop automation
tree, it might receive tree data for a child tree before the child tree's
accessibility data is reset via
chrome.automation.enableFrame.
This results in the client extension tree having an embeddedObject node with one
child with role unknown.
Fix this by always resetting a child tree root that has unknown role

- work around webview focus issues by explicitly always checking the ancestors
we've crossed into and always focusing first embeddedObject nodes. This should
be removed once webview handles propagating upwards focus from descendants
correctly.

BUG=660390
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
Fix reset and focus issues in OOBE

- if an extension is toggled off then on, and re-requests the desktop automation
tree, it might receive tree data for a child tree before the child tree's
accessibility data is reset via
chrome.automation.enableFrame.
This results in the client extension tree having an embeddedObject node with one
child with role unknown.
Fix this by always resetting a child tree root that has unknown role

- work around webview focus issues by explicitly always checking the ancestors
we've crossed into and always focusing first embeddedObject nodes. This should
be removed once webview handles propagating upwards focus from descendants
correctly.

BUG=660390
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Committed: https://crrev.com/20d6d96d1e472287cb4270b1d6c8b48973994fcd
Cr-Commit-Position: refs/heads/master@{#429978}
==========

[commit-bot: I haz the power, 2016-11-04 20:00:21]

Patchset 1 (id:??) landed as
https://crrev.com/20d6d96d1e472287cb4270b1d6c8b48973994fcd
Cr-Commit-Position: refs/heads/master@{#429978}