progressbar valuenow allows invalid type

[guest]

(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

[guest]

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

[Adam Peller]

Simon, your thoughts on this?

[simonjb]

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.

[guest]

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.

[guest]

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 '%'

[simonjb]

"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

​https://bugzilla.mozilla.org/show_bug.cgi?id=400737#c9

[davidb]

Perhaps we should fix this soonish since folks will be looking to dojo for ARIA precedent. I see two bits of work:

1. fix any tests to use only numbers for valuenow, valuemin, valuemax.
2. (Optionally) validate and report a type error if necessary.

[simonjb]

(In [11239]) Set valuenow to this.progress (and set valuemin and valuemax) rather than using this.report(). Fixes #4185: progressbar valuenow allows invalid type.