Closed
Bug 413376
Opened 18 years ago
Closed 18 years ago
value of slider not available via MSAA if it has an onclick handler
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: simon.bates, Assigned: aaronlev)
References
Details
Attachments
(2 files)
|
291 bytes,
text/html
|
Details | |
|
1.10 KB,
patch
|
MarcoZ
:
review+
mtschrep
:
approval1.9+
|
Details | Diff | Splinter Review |
To reproduce:
1. open the attachment slider.html
2. open the Microsoft Inspect tool
3. tab to "slider without onclick"; value: "10" displayed correctly in Inspect
4. tab to "slider with onclick"
Expected:
* value: "10"
Actual:
* value: none [false]
Tested with:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2008012104 Minefield/3.0b3pre
I also tested on Ubuntu Linux and I could read the value via Accerciser for both sliders.
| Reporter | ||
Comment 1•18 years ago
|
||
attached slider.html testcase
Comment 2•18 years ago
|
||
Confirmed also with JAWS. It doesn't read any value for the second slider even when its value is changed.
Blocks: fox3access
| Assignee | ||
Comment 3•18 years ago
|
||
Attachment #298327 -
Flags: review?(marco.zehe)
Comment 4•18 years ago
|
||
Comment on attachment 298327 [details] [diff] [review]
Simple fix: upcall to try and get WAI value before we check to see if it is a link (which gets URL value) or gets no value
r=me
Attachment #298327 -
Flags: review?(marco.zehe) → review+
| Assignee | ||
Updated•18 years ago
|
Attachment #298327 -
Flags: review?
| Assignee | ||
Updated•18 years ago
|
Attachment #298327 -
Flags: approval1.9?
| Assignee | ||
Updated•18 years ago
|
Attachment #298327 -
Flags: review?
Updated•18 years ago
|
Attachment #298327 -
Flags: approval1.9? → approval1.9+
| Assignee | ||
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 5•18 years ago
|
||
Verified using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•