Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#24491 closed Bug (duplicate)

Admin's "no" icon is incorrect and should be replaced

Reported by: Daniele Procida Owned by: nobody
Component: contrib.admin Version: 1.7
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: yes

Description

The admin uses pretty yes/no icons:

The "no" icon is incorrect; https://github.com/django/django/blob/master/django/contrib/admin/static/admin/img/icon-no.gif means "no entry", not "no".

This leads to some confusing interface cases: a boolean field called "locked" or "restricted" for example, will show a no entry sign when an item is not locked or restricted - the sign itself denotes restricted access to something.

While the "yes" tick is commonly-recognised, there is no good symbol for "no" - most negative symbols denote prohibition, and I can't think of any that imply simple negation.

Even a red cross in a box [x] isn't adequate, because crosses are also used to check boxes in many interfaces, and some people are red-green colourblind.

My suggestion is to change both symbols, so that "yes" is a green tick in a green box, and and "no" is an unticked red box.

Change History (3)

comment:1 by Tim Graham, 10 years ago

Resolution: duplicate
Status: newclosed

Could you raise this as part of the work elky is doing on the "new look"? https://groups.google.com/d/msg/django-developers/HJAikaEBqJ4/L6pU8iIi6uMJ

As this change will require updating the documentation screenshots in ref/contrib/admin/index.txt and intro/tutorial02.txt, it seems like a good opportunity to combine efforts.

comment:2 by Daniele Procida, 10 years ago

I've raised it there - https://github.com/elky/django-flat-theme/issues/3 - but I don't think it should depend on that (what if that project stalls, for example?).

comment:3 by Tim Graham, 10 years ago

I expect it will be merged in a matter of weeks. If not, I'll consider reopening this ticket. I'd rather not create conflicts/duplicated effort by leaving this open and tempting someone to pick it up now.

Note: See TracTickets for help on using tickets.
Back to Top