Description: This component relates to bugs in our support for accessibility APIs on the various platforms. Accessibility APIs allow 3rd party products, such as screen readers used by visually impaired users, to communicate with our content and UI. The APIs we support specifically are MSAA on Windows and
ATK on UNIX/Linux (Apple has not yet published specs for an accessibility API on OS X). This component is not for keyboard, focus or any accessibility bugs other than those relating to the APIs we export.

re: "I don't think that should fail under normal cases" ...
I patterned these SelectRow() / SelectCol() methods on the existing UnselectRow () / UnselectCol() methods, which don't have warnings. If you lean towards my keeping warnings in Select methods, should I retro-fit them back into the Unselect methods?
re: if (control) { ... I don't think you need to add this check ...
Again, this is how the Unselect() function currently is coded, so I sought uniformity.
If you are flexible with your thoughts here, I'd like to leave the patch as I now have it. If you strongly disagree, then I'd feel better at least making consistent changes for both the Select() and Unselect() methods.

(In reply to Mark Capella [:capella] from comment #4)
> re: "I don't think that should fail under normal cases" ...
>
> I patterned these SelectRow() / SelectCol() methods on the existing
> UnselectRow () / UnselectCol() methods, which don't have warnings. If you
> lean towards my keeping warnings in Select methods, should I retro-fit them
> back into the Unselect methods?
I'd probably prefer that happen some day, but fixing them doesn't seem terribly urgent.
> re: if (control) { ... I don't think you need to add this check ...
>
> Again, this is how the Unselect() function currently is coded, so I sought
> uniformity.
consistantly wrong is worse than sometimes right and inconsnistant.
> If you are flexible with your thoughts here, I'd like to leave the patch as
> I now have it. If you strongly disagree, then I'd feel better at least
> making consistent changes for both the Select() and Unselect() methods.
why? what's wrong with just fixing the current issue the best way possiblew? THere are certainly inconsistant things, but if you try and fix them all at once you'll never get it done. If you really can't stand the thought of a little bit of inconsistancy I guess I don't mind fixing them now since its small, and sort of maybe a little related, but that seems like enough change I'd probably get it reviewed again, were as if you just change these methods I wouldn't bother.