#4185 closed defect (fixed)
progressbar valuenow allows invalid type
Reported by: | guest | Owned by: | simonjb |
---|---|---|---|
Priority: | high | Milestone: | 1.0 |
Component: | Accessibility | Version: | 0.9 |
Keywords: | Cc: | davidb | |
Blocked By: | Blocking: |
Description (last modified by )
(Note: Summary used to be "Dojo progressbars are not triggering object:property-change:accessible-value events")
The Mozilla guys recently fixed the AT-SPI Value interface bug https://bugzilla.mozilla.org/show_bug.cgi?id=389851 which affected both sliders and progressbars. Dojo sliders check out fine but the progressbars are not triggering AT-SPI object:property-change:accessible-value events. Here is a link to a working progressbar http://www.mozilla.org/access/dhtml/progressbar
Attachments (1)
Change History (12)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Milestone: | → 1.0 |
---|---|
Owner: | changed from anonymous to simonjb |
Simon, your thoughts on this?
comment:3 Changed 14 years ago by
It looks to me like the Dojo ProgressBar value is being read by MSAA from Minefield on Windows. It would be good to try out the ProgressBar on Linux to see what differences there are between the Dojo ProgressBar and the one at http://www.mozilla.org/access/dhtml/progressbar. The correct fix here might be to Mozilla rather than Dojo but I'm not entirely sure yet.
comment:4 Changed 14 years ago by
Component: | General → Accessibility |
---|
comment:5 Changed 13 years ago by
Milestone: | 1.0 → 1.1 |
---|
comment:6 Changed 13 years ago by
Part of the problem may be that two similar roles are set. Both wairole=progressbar and role=progressbar are set as seen by the DOM inspector.
comment:7 Changed 13 years ago by
cross reference with this Mozilla bug https://bugzilla.mozilla.org/show_bug.cgi?id=400737
The problem lies in the fact that valuenow should report a float and not a value containing '%'
comment:8 Changed 13 years ago by
"We need to fix Dojo to use a number, and fix the ARIA spec so that it requires that valuenow/valuemin/valuemax is a number. I've send a note to the PFWG to fix the spec."
Aaron Leventhal
comment:9 Changed 13 years ago by
Cc: | davidb added |
---|---|
Description: | modified (diff) |
Summary: | Dojo progressbars are not triggering object:property-change:accessible-value events → progressbar valuenow allows invalid type |
Perhaps we should fix this soonish since folks will be looking to dojo for ARIA precedent. I see two bits of work:
- fix any tests to use only numbers for valuenow, valuemin, valuemax.
- (Optionally) validate and report a type error if necessary.
Changed 13 years ago by
comment:10 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:11 Changed 13 years ago by
Milestone: | 1.1 → 1.0 |
---|
I made an error. The AT-SPI object:property-change:accessible-value events are being triggered. The problem is that IValue.currentValue is always 0.0