#2885 closed defect (fixed)
AutoCompleter: Should not be able to push a disabled arrow
| Reported by: | guest | Owned by: | haysmark |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Widgets | Version: | 0.9 |
| Keywords: | Cc: | [email protected]… | |
| Blocked By: | Blocking: |
Description
When you click the disabled arrow in the AutoCompleter? test, you can clearly click the arrow. The style of the arrow should not change when the AutoCompleter? is disabled.
Change History (5)
comment:1 Changed 13 years ago by
| Component: | General → Widgets |
|---|---|
| Owner: | changed from anonymous to [email protected]… |
comment:2 Changed 13 years ago by
| Owner: | changed from [email protected]… to haysmark |
|---|
comment:3 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:4 Changed 13 years ago by
(In [8530]) earlier checkins seem to have completely busted InlineEditBox?. This seems to fix. Refs #2885, #2309
Also, we didn't write the style guide because we were looking for something to do one sunny saturday. Compliance is not optional. Continued variances may result in commit privs being revoked. You have been warned.
comment:5 Changed 13 years ago by
I discussed the context of this checkin w/ Doug, and given the context it seems a reasonable thing to have done. Improved communication on all sides will prevent this from being an issue in the future. Thanks to Doug for helping me understand his constrains.
(In [8458]) Fixes #2885, #2309. AutoCompleter? now inherits from SerializableTextbox?. DateTextbox? now has a Calendar drop down, but still needs RangeBoundTextbox? min/max code working. Calendar now works under 0.9.