Context Navigation

Changes between Initial Version and Version 9 of Ticket #16304

Timestamp:: Oct 15, 2012, 3:47:26 PM (12 years ago)
Author:: Łukasz Rekucki
Comment:: Is there any reason why this is added only to CharField? placeholder is more of a widget thing, so it shouldn't matter on what type of field I define it as long as I use a widget that can render it. placeholder is also legal on <textarea> not only variations of <input type="...">.

-              initial
+              v9
 To do this in Django currently, you have to do something like:
+{{{#!python
 comment = forms.CharField(max_length=200, widget=forms.TextInput({ "placeholder": "Text!"}))
+}}}
 However, to do this with a ModelForm is much more complicated: http://bitkickers.blogspot.com/2010/09/django-html5-input-placeholders.html
 …
 I suggest that there should be an easier way to set placeholder text in form fields and model form fields:
+{{{#!python
 comment = forms.CharField(max_length=200, placeholder="Text!")
+}}}
 (This would also be a good starting point for other new HTML5 input elements, such as 'required' and 'email', but those should be separate tickets. The code would be very similar though.)