Opened 13 years ago
Closed 13 years ago
#5543 closed defect (fixed)
ARIA valuenow property only used for numeric values
Reported by: | Becky Gibson | Owned by: | Becky Gibson |
---|---|---|---|
Priority: | high | Milestone: | 1.1 |
Component: | Accessibility | Version: | 1.0 |
Keywords: | a11y aria ff3 | Cc: | |
Blocked By: | Blocking: |
Description
In order to support the Linux a11y API's the valuenow property in Firefox 3 will only support numeric values. Thus, the setValue() api in _FormWidget needs to be updated as well as other uses where a string is being used as the valuenow.
check combobox, progressbar, slider, and spinner as well.
Attachments (1)
Change History (6)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
explanation of 5543.patch.
remove setting of valuenow from _FormValidationWidget.setValue() since not all FormValidation? Widgets are numeric. removed _FormValueWidget.forWaiValuenow() - it is no longer needed
added setting of valuenow to _slider.setValue(). Slider needs to set valuenow since setting has been removed from FormBalidationwidget?. added setting of valuemin, valuemax to _Slider.postCreate() - it was an error that these were not being set previously.
removed textBox.forWaiValuenow() as it is no longer needed since textbox is generally not numeric.
added RangeBoundTextbox?.setValue function to set valuenow since it deals with numeric text boxes.
comment:3 Changed 13 years ago by
Status: | new → assigned |
---|
comment:5 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
(In [11980]) refs #5543 removed use of valuenow in combobox; update of value attribute of editfield is sufficient for a11y