mirror of
https://github.com/django/django.git
synced 2025-10-24 06:06:09 +00:00
Fixed 32956 -- Lowercased spelling of "web" and "web framework" where appropriate.
This commit is contained in:
committed by
Mariusz Felisiak
parent
acde917456
commit
1024b5e74a
@@ -77,7 +77,7 @@ should be used only for requests that do not affect the state of the system.
|
||||
``GET`` would also be unsuitable for a password form, because the password
|
||||
would appear in the URL, and thus, also in browser history and server logs,
|
||||
all in plain text. Neither would it be suitable for large quantities of data,
|
||||
or for binary data, such as an image. A Web application that uses ``GET``
|
||||
or for binary data, such as an image. A web application that uses ``GET``
|
||||
requests for admin forms is a security risk: it can be easy for an attacker to
|
||||
mimic a form's request to gain access to sensitive parts of the system.
|
||||
``POST``, coupled with other protections like Django's :doc:`CSRF protection
|
||||
@@ -115,7 +115,7 @@ Forms in Django
|
||||
We've described HTML forms briefly, but an HTML ``<form>`` is just one part of
|
||||
the machinery required.
|
||||
|
||||
In the context of a Web application, 'form' might refer to that HTML
|
||||
In the context of a web application, 'form' might refer to that HTML
|
||||
``<form>``, or to the Django :class:`Form` that produces it, or to the
|
||||
structured data returned when it is submitted, or to the end-to-end working
|
||||
collection of these parts.
|
||||
|
||||
@@ -2,11 +2,11 @@
|
||||
Form Assets (the ``Media`` class)
|
||||
=================================
|
||||
|
||||
Rendering an attractive and easy-to-use Web form requires more than just
|
||||
HTML - it also requires CSS stylesheets, and if you want to use fancy
|
||||
"Web2.0" widgets, you may also need to include some JavaScript on each
|
||||
page. The exact combination of CSS and JavaScript that is required for
|
||||
any given page will depend upon the widgets that are in use on that page.
|
||||
Rendering an attractive and easy-to-use web form requires more than just
|
||||
HTML - it also requires CSS stylesheets, and if you want to use fancy widgets,
|
||||
you may also need to include some JavaScript on each page. The exact
|
||||
combination of CSS and JavaScript that is required for any given page will
|
||||
depend upon the widgets that are in use on that page.
|
||||
|
||||
This is where asset definitions come in. Django allows you to
|
||||
associate different files -- like stylesheets and scripts -- with the
|
||||
@@ -16,7 +16,7 @@ Calendar widget. This widget can then be associated with the CSS and
|
||||
JavaScript that is required to render the calendar. When the Calendar
|
||||
widget is used on a form, Django is able to identify the CSS and
|
||||
JavaScript files that are required, and provide the list of file names
|
||||
in a form suitable for inclusion on your Web page.
|
||||
in a form suitable for inclusion on your web page.
|
||||
|
||||
.. admonition:: Assets and Django Admin
|
||||
|
||||
|
||||
Reference in New Issue
Block a user