Context Navigation

Changes between Initial Version and Version 1 of Ticket #27386, comment 4

initial	v1
1	1	Yes, changing this could add a minor backwards compatibility problem; something probably not really noticeable and if, easy to fix.
2	2
3		I looked at the code. We presumably should add another tag to ``django.contrib.admin.helpers.AdminReadonlyField.__init__`` named ``is_callable`` which is ``True`` for callable fields. Then in the templates, we'd have to add another ``{% if field.is_callable %}`` and only wrap the content inside ``<p>..</p>`` it that's false.
	3	I looked at the code. We presumably should add another tag to `django.contrib.admin.helpers.AdminReadonlyField.__init__` named `is_callable` which is `True` for callable fields. Then in the templates, we'd have to add another `{% if field.is_callable %}` and only wrap the content inside `<p>..</p>` it that's false.
4	4
5	5	If this proposal is accepted, I will implement it right now.