Merge to M50: Fix accessible focus state on menu bar container.

Merge to M50: Fix accessible focus state on menu bar container.

When the Chrome menu is open, we use a role of "menu bar" for the outer
pop-up container, "menu" inside of that, and "menu item" for each item.
One screen reader, NVDA, ignores focus events inside the menu unless the
menu bar indicates that it's focused.

This code was moved from cross-platform code to Windows-specific code in
r376339 when we switched to keeping track of focus globally, but
unfortunately it broke because we don't keep track of focus inside
the menu pop-up.

So for now as a quick fix, just mark the menu bar role as focused when
visible. This will work fine because this is the only place we use the
menu bar role and it's only visible when the menu is popped up. Later
a better fix would be to properly track focus inside the menu pop-up.

Tested manually with NVDA.

BUG=593589
Review URL: https://codereview.chromium.org/1801183002

Cr-Commit-Position: refs/heads/master@{#381320}
(cherry picked from commit 34bf4c64e98f95f62d37891f45a945076c506a56)

Committed: https://chromium.googlesource.com/chromium/src/+/d301ea79b9a13f2d6dbed1afbf1b0ba4b8675e74

[dmazzoni, 2016-03-24 04:38:28]

Description was changed from

==========
Merge to M50: Fix accessible focus state on menu bar container.

When the Chrome menu is open, we use a role of "menu bar" for the outer
pop-up container, "menu" inside of that, and "menu item" for each item.
One screen reader, NVDA, ignores focus events inside the menu unless the
menu bar indicates that it's focused.

This code was moved from cross-platform code to Windows-specific code in
r376339 when we switched to keeping track of focus globally, but
unfortunately it broke because we don't keep track of focus inside
the menu pop-up.

So for now as a quick fix, just mark the menu bar role as focused when
visible. This will work fine because this is the only place we use the
menu bar role and it's only visible when the menu is popped up. Later
a better fix would be to properly track focus inside the menu pop-up.

Tested manually with NVDA.

BUG=593589

Review URL: https://codereview.chromium.org/1801183002

Cr-Commit-Position: refs/heads/master@{#381320}
(cherry picked from commit 34bf4c64e98f95f62d37891f45a945076c506a56)
==========

to

==========
Merge to M50: Fix accessible focus state on menu bar container.

When the Chrome menu is open, we use a role of "menu bar" for the outer
pop-up container, "menu" inside of that, and "menu item" for each item.
One screen reader, NVDA, ignores focus events inside the menu unless the
menu bar indicates that it's focused.

This code was moved from cross-platform code to Windows-specific code in
r376339 when we switched to keeping track of focus globally, but
unfortunately it broke because we don't keep track of focus inside
the menu pop-up.

So for now as a quick fix, just mark the menu bar role as focused when
visible. This will work fine because this is the only place we use the
menu bar role and it's only visible when the menu is popped up. Later
a better fix would be to properly track focus inside the menu pop-up.

Tested manually with NVDA.

BUG=593589

Review URL: https://codereview.chromium.org/1801183002

Cr-Commit-Position: refs/heads/master@{#381320}
(cherry picked from commit 34bf4c64e98f95f62d37891f45a945076c506a56)

Committed:
https://chromium.googlesource.com/chromium/src/+/d301ea79b9a13f2d6dbed1afbf1b...
==========

[dmazzoni, 2016-03-24 04:38:30]

Committed patchset #1 (id:1) manually as
d301ea79b9a13f2d6dbed1afbf1b0ba4b8675e74.