Changes between Initial Version and Version 4 of Ticket #8785
- Timestamp:
- Nov 8, 2012, 9:19:55 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #8785
-
Property
Status
changed from
new
toassigned
- Property Owner set to k_borchers
-
Property
Milestone
changed from
1.10.0
togit
-
Property
Status
changed from
-
Ticket #8785 – Description
initial v4 1 There's no reason for the `value` option to ever be invalid. We should force it to a valid value on init and whenever `m in`, `max`, or `value` changes. The validation on change needs to occur in `_setOptions()` so that we properly handle a call like `.progressbar( "option", { value -6, min: -10 } )` which would try to set the value below the current min.1 There's no reason for the `value` option to ever be invalid. We should force it to a valid value on init and whenever `max`, or `value` changes. The validation on change needs to occur in `_setOptions()` so that we properly handle a call like `.progressbar( "option", { value 120, max: 150 } )` which would try to set the value above the current max.