Issue 2243: Accessibility tests' use of indices to locate views is
error-prone
http://code.google.com/p/chromium/issues/detail?id=2243
New issue report by [EMAIL PROTECTED]:
It's very easy to break the accessibility tests in ways that are not
immediately obvious how to fix. This is because the tests locate views in
the browser window using indices and predefined containers. The
documentation in chrome/test/accessibility/constants.h etc is also a bit
sparse as to the structure the tests expect.
Ideally, all of these controls would have view IDs, and the tests would
just use the IDs to locate the views.
Issue attributes:
Status: Assigned
Owner: [EMAIL PROTECTED]
Labels: Type-Bug Pri-2 OS-Windows Area-BrowserUI
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
