Opened 14 years ago
Closed 12 years ago
#14874 closed Bug (wontfix)
remove js-confirms on changelist
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | contrib.admin | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | yes |
Description
see http://code.djangoproject.com/browser/django/trunk/django/contrib/admin/media/js/actions.js:
just delete line 104 to 126.
why? because
a) trusted editors should know what they do.
b) triggering the change-function of form-fields may not capture all changes.
c) and probably most important: we don´t do that on the change-form. it´s all about coherence.
Change History (7)
comment:1 by , 14 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
comment:2 by , 14 years ago
| Severity: | → Normal |
|---|---|
| Type: | → Bug |
comment:3 by , 13 years ago
| UI/UX: | set |
|---|
comment:7 by , 12 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
apollo13 and me have discussed this at the Django sprint in Berlin and don't see enough reasons to remove this user facing feature. Inconsistencies in the code doesn't mean we should remove it completely, but rather consider fixing the other places to apply the same.
Note:
See TracTickets
for help on using tickets.
This is a fair request, but it needs some discussion as there are usability implications. I recommend you to bring this question up on the django-developers mailing list (1) and seek opinions from developers who are using this functionality in production with clients.
(1) http://groups.google.com/group/django-developers/topics