Closed
Bug 379875
Opened 17 years ago
Closed 17 years ago
Expose checkable object property
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
People
(Reporter: aaronlev, Assigned: aaronlev)
References
(Blocks 1 open bug)
Details
(Keywords: access)
Attachments
(2 files, 1 obsolete file)
1.47 KB,
patch
|
Details | Diff | Splinter Review | |
1.30 KB,
patch
|
davidb
:
review+
|
Details | Diff | Splinter Review |
We may want to turn our internal CHECKABLE property into an object property "checkable"="true". Do we need this? Or are the roles sufficient? Checkable object ATK role Menu item ROLE_CHECK_MENU_ITEM or ROLE_RADIO_MENU_ITEM List item ROLE_CHECK_BOX inside a ROLE_LIST? Tree item ROLE_CHECK_BOX inside a tree? (Instead of ROLE_TABLE_CELL) This is separate from the "cycles"="true" object property which David Bolter fixed in bug 368012.
Assignee | ||
Comment 1•17 years ago
|
||
Assignee | ||
Comment 2•17 years ago
|
||
Attachment #263918 -
Attachment is obsolete: true
Assignee | ||
Comment 3•17 years ago
|
||
Attachment #270862 -
Flags: review?(david.bolter)
Comment 4•17 years ago
|
||
Comment on attachment 270862 [details] [diff] [review] We already have state in this part of the code, so use it to expose checkable there looks good.
Attachment #270862 -
Flags: review?(david.bolter) → review+
Assignee | ||
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•