diff options
| author | dtseng@chromium.org <dtseng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-19 18:04:59 +0000 |
|---|---|---|
| committer | dtseng@chromium.org <dtseng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-19 18:04:59 +0000 |
| commit | f2c4ee3627e6039fd42bd7c0c93e902b72653449 (patch) | |
| tree | 9f314a639647688d497013f76bbe929b95210523 /chrome/browser/browser_process.h | |
| parent | 545b13041b565fef5b289030207f5244afe76c07 (diff) | |
| download | chromium_src-f2c4ee3627e6039fd42bd7c0c93e902b72653449.zip chromium_src-f2c4ee3627e6039fd42bd7c0c93e902b72653449.tar.gz chromium_src-f2c4ee3627e6039fd42bd7c0c93e902b72653449.tar.bz2 | |
Another take on menu's. This uses the hosting menu scroll view container as a menubar on which we can fire MENUSTART and MENUEND events. The end result is that we now have the following scenario when a user opens a menu.
1. focus lands on the menu button.
2. down arrow.
3. A "chromium" menu item appears.
4. down arrow (or enter).
5. The first menu item gets focused.
The only differences from what we currently have is Jaws/NVDA no longer say "context menu opened" or "applications". The first real menuitem also doesn't get focused when the menu shows.
BUG=none.
TEST=use NVDA and Jaws to navigate the menu's (opening, closing, submenus, accelerators).
Review URL: http://codereview.chromium.org/3155029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56715 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/browser_process.h')
0 files changed, 0 insertions, 0 deletions