mirror of
https://github.com/django/django.git
synced 2025-10-31 09:41:08 +00:00
[1.2.X] Fixed #11509 -- Modified usage of "Web" to match our style guide in various documentation, comments and code. Thanks to timo and Simon Meers for the work on the patch
Backport of r14069 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.2.X@14072 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
@@ -197,7 +197,7 @@ Customizing widget instances
|
||||
When Django renders a widget as HTML, it only renders the bare minimum
|
||||
HTML - Django doesn't add a class definition, or any other widget-specific
|
||||
attributes. This means that all 'TextInput' widgets will appear the same
|
||||
on your web page.
|
||||
on your Web page.
|
||||
|
||||
If you want to make one widget look different to another, you need to
|
||||
specify additional attributes for each widget. When you specify a
|
||||
@@ -222,7 +222,7 @@ each widget will be rendered exactly the same::
|
||||
<tr><th>Comment:</th><td><input type="text" name="comment" /></td></tr>
|
||||
|
||||
|
||||
On a real web page, you probably don't want every widget to look the same. You
|
||||
On a real Web page, you probably don't want every widget to look the same. You
|
||||
might want a larger input element for the comment, and you might want the 'name'
|
||||
widget to have some special CSS class. To do this, you use the ``attrs``
|
||||
argument when creating the widget:
|
||||
|
||||
Reference in New Issue
Block a user