#33437: Add possibility to render fields individually using as_p, a_table and
as_ul
----------------------------------+--------------------------------------
Reporter: Christophe Henry | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by David Smith):
Thank you for your proposal. I have a few comments (mainly concerns,
sorry) on this.
The first is that the current `as_` methods are not recommended due to
accessibility concerns see #32339. I don't think we should be adding
additional features to something that we are not willing to recommend,
even if we stop short of removing the due to backward compatibility
concerns. Having said that it could be appropriate if an `as_div()` render
style is introduced.
I wonder about having the same named functions on both the field and the
form. I'd have thought that would lead to some confusion?
I appreciate this is about whole forms rather than fields is I wonder how
far the new template based form rendering API could meet this need.
--
Ticket URL: <https://code.djangoproject.com/ticket/33437#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.290a7b4c36cd67c4ef4f04f3187f9b96%40djangoproject.com.
