Closed
Bug 369640
Opened 17 years ago
Closed 17 years ago
ARIA multiselectable vs. multiselect naming mistake
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
(1 file)
6.60 KB,
patch
|
davidb
:
review+
|
Details | Diff | Splinter Review |
I just noticed that for some roles we support the property called "multiselectable" and for others we call it "multiselect". The ARIA states doc calls it "multiselectable" http://www.w3.org/TR/aria-state/
Assignee | ||
Comment 1•17 years ago
|
||
I think we should support both and deprecate one, since our docs have said we support one or the other in different places.
Assignee | ||
Comment 2•17 years ago
|
||
Actually, no one's using this yet. I'm going to keep the code simple and just support the correct name.
Assignee | ||
Comment 3•17 years ago
|
||
Attachment #257856 -
Flags: review?(david.bolter)
Comment 4•17 years ago
|
||
Comment on attachment 257856 [details] [diff] [review] Use "multiselectable" Looks good.
Attachment #257856 -
Flags: review?(david.bolter) → review+
Assignee | ||
Comment 5•17 years ago
|
||
Made one extra change of kNameSpaceID_None to the WAI properties namespace.
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
•