#23690: Docs for Rendering fields manually <label for="...."> showing static
rather
than dynamic code
-------------------------------------+-------------------------------------
Reporter: awidgery | Owner: nmundar
Type: | Status: closed
Cleanup/optimization | Version: 1.7
Component: Documentation | Resolution: fixed
Severity: Normal | Triage Stage: Ready for
Keywords: | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by nmundar <neven.mundar@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"48515ee1f7bec437544a0a958332483298f4028b"]:
{{{
#!CommitTicketReference repository=""
revision="48515ee1f7bec437544a0a958332483298f4028b"
Fixed #23690 - fixed examples of manual rendering of form fields
Documentation for rendering form fields manually is now updated to use
fields id_for_label instead of hardcoded values with additional mention of
label_tag for alternative generation of complete label tag.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23690#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.b847f1cdfd4aaa286c1d22efd15a6d7a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
