Adrian Holovaty wrote:
> Hi Johannes,
>
> Could you update your code to at least revision 4296? I believe I've
> fixed the problem. Thanks again for reporting it.
Hi Adrian
Thanks for this quick response and fix. I keep up to date on trunk
since I'm really interested in the development there.
There was another question about choices coming up: Is it intended that
input fields in the html output of choices is nested inside the labels
tag? In my opinion it's better to have
<label id_for="">blub</label><input/>
instead of
<label id_for="">blub <input/></label>
In the first one i could just hide the labels of choices via css if
necessary. The second needs a hack in the widget which isn't that easy
in a template.
-johannes
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
