Opened 9 years ago
Closed 7 years ago
#11380 closed defect (patchwelcome)
MultiSelect: A readOnly widget is not really read-only
| Reported by: | riceyeh | Owned by: | Douglas Hays |
|---|---|---|---|
| Priority: | high | Milestone: | future |
| Component: | Dijit - Form | Version: | 1.4.3 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Setting a dijit.form.MultiSelect? widget readOnly will not really make it read-only. Although the cursor is changed to 'not-allowed' when hovering over it, it is still allowed to change the selected options.
Regards, Rice
Change History (7)
comment:1 Changed 9 years ago by
| Component: | General → Dijit |
|---|---|
| Owner: | anonymous deleted |
| Summary: | A readOnly dijit.form.MultiSelect widget is not really read-only → MultiSelect: A readOnly widget is not really read-only |
comment:2 Changed 8 years ago by
| Owner: | set to Douglas Hays |
|---|
comment:3 Changed 8 years ago by
| Milestone: | tbd → 1.7 |
|---|
comment:4 Changed 8 years ago by
| Component: | Dijit → Dijit - Form |
|---|
comment:5 Changed 8 years ago by
| Milestone: | 1.7 → future |
|---|
comment:6 Changed 7 years ago by
This is marked as high priority and latest change is 12 months ? I vote for fix, please !
comment:7 Changed 7 years ago by
| Resolution: | → patchwelcome |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
This is going to take a lot of code to get right like connecting to several events to make sure there's no way to change the value, and monitoring a multitude of key combinations (some of which are device and platform specific). This widget uses a native HTML SELECT and that element doesn't support readOnly. Marking as future in case anyone wants to donate a patch and associated testcase.