--- a/doc/upgrading.txt	Wed Jan 22 10:10:39 2025 -0500
+++ b/doc/upgrading.txt	Wed Feb 19 12:38:06 2025 +0100
@@ -227,71 +227,74 @@
 Enable use of native date inputs (optional)
 -------------------------------------------
 
-Roundup now uses native date or datetime-local inputs for Date()
-properties. These inputs take the place of the text input and
-calendar popup from earlier Roundup versions. Modern browsers
-come with a built-in calendar for date selection, so the
-``(cal)`` calendar link is no longer needed. These native inputs
-show the date based on the browser's locale and translate terms
-into the local language.
-
-If you do nothing, simple uses of the field() method will
-generate date inputs to allow selection of a date.  Input fields
-for Date() properties will not have the ``(cal)`` link
-anymore. Complex uses will not be upgraded and will operate like
-earlier Roundup versions.
-
-To upgrade all date properties, there are four changes to make:
-
-  1. Replace ``field`` calls with ``field_time`` where needed.
-
-  2. Remove the format argument from field() calls on Date()
+Roundup now can use native ``date`` or ``datetime-local`` inputs for
+``Date()`` properties. These inputs take the place of the text input and
+calendar popup from earlier Roundup versions. Modern browsers come with
+a built-in calendar for date selection, so the ``(cal)`` calendar link
+is no longer needed. These native inputs show the date based on the
+browser's locale and translate terms into the local language.
+
+Note that the date format is tied to the language setting in most
+browsers, with some browsers you need special configurations to make the
+browser use the operating system date format.
+
+By default the old input mechanism (using type=text inputs) is used.
+To enable native date input you need to set the config variable ::
+
+  use_browser_date_input = yes
+
+in section ``[web]`` in the ``config.ini`` file.
+ 
+If native date input is used, simple uses of the ``field()`` method will
+generate ``datetime-local`` inputs to allow selection of a date and time.
+Input fields for ``Date()`` properties will not have the ``(cal)`` link
+anymore. If fields should only use a date (without time) you can specify
+the parameter ``display_time=no`` in ``schema.py`` for a ``Date()``
+property (the default is ``yes``). This will use ``date`` inputs in the
+generated html to select a date only. If you need this only for a single
+date, the ``field()`` method now has a boolean parameter
+``display_time`` (which by default is set to the ``display_time``
+parameter of ``Date()``)
+
+Complex uses using a ``format`` specification in ``field()`` will not be
+upgraded and will operate like earlier Roundup versions. In addition the
+``format`` can now also be specified in the ``Date()`` constructor.
+
+To upgrade all date properties, there are five changes to make:
+
+  1. Configure ``use_browser_date_input = yes`` in section ``[web]`` in
+     ``config.ini``
+
+  2. Optionally add ``display_time = no`` in the schema for Date()
+     properties that should have no time displayed
+
+  3. Remove the format argument from field() calls on Date()
      properties.
 
-  3. Remove popcal() calls.
-
-  4. Include datecopy.js in page.html.
-
-Use field_time() where needed
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-The format used by ``field`` does not include hours, minutes or
-seconds. If your users need to enter times, you should change
-these calls to use ``field_time``. The arguments are the same as
-for field.
+  4. Remove popcal() calls.
+
+  5. Include datecopy.js in page.html.
+
+The ``display_time`` option
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Both the ``Date()`` constructor and the ``field`` call take a
+``display_time`` option which by default is ``yes`` in the ``Date()``
+constructor and ``True`` in ``field``. The ``display_time`` setting of
+``Date()`` is inherited by the html property, so it doesn't need to be
+specified in each ``field()`` call for this property.
+
+When ``display_time`` is off, the date field does not include hours,
+minutes or seconds.
 
 Remove format argument
 ~~~~~~~~~~~~~~~~~~~~~~
 
-Speaking of arguments, avoid setting the date format if you want
-to use native date inputs. The date value needs a specific format
-for date or datetime-local inputs. If you include the `format`
-argument in the `field` method, it should be removed.
-
-The `field` method uses the format ``%Y-%m-%d``.  The
-``field_time`` method uses the format ``%Y-%m-%dT%H:%M:%S``. If
-you use these exact formats, Roundup will accept them and use a
-native date input.
-
-.. highlight:: text
-
-If you use an format that doesn't match, you will see a text
-input and a logged warning message like::
-
-  Format '%Y-%m' prevents use of modern date input.
-  Remove format from field() call in template test.item.
-  Using text input.
-
-.. highlight:: default
-
-The log message will appear if your logging level is set to
-WARNING or lower. (Refer to your tracker's :ref:`config.ini
-logging section <config-ini-section-logging>` for details on
-logging levels.)
-
-If you want to use a text input for a specific date format, you
-can add ``type="text"`` to the field() argument list to suppress
-the warning. By default using a format argument will show the
+Speaking of arguments, avoid setting the date ``format`` if you want to
+use native date inputs. If you include the `format` argument in the
+`field` method, it should be removed.
+
+By default using a format argument will show the
 popup calendar link. You can disable the link by setting
 ``popcal=False`` in the field() call. If you have::
 
@@ -301,38 +304,26 @@
 changing it to::
 
   tal:content="structure python:context.duedate.field(
-               type='text',
                placeholder='YYYY-MM, format='%Y-%m',
                popcal=False)"
 
 will generate the input as in Roundup 2.4 or earlier without a
 popcal link.
 
-.. _revert_input_to_text:
-
-If you are using a path expression like::
-
-  tal:content="context/duedate/field"
-
-change it to::
-
-  tal:content="structure python:context.duedate.field(
-               type='text')"
-
-to get the input from before Roundup 2.5 with a popcal link.
-
 Remove popcal
 ~~~~~~~~~~~~~
 
-If you use the ``popcal()`` method directly in your templates, you
-can remove them. The browser's native date selection calendar can
+if you have enabled date input types in the configuration and you
+use the ``popcal()`` method directly in your templates, you
+should remove them. The browser's native date selection calendar should
 be used instead.
 
 Add copy/paste/edit on double-click using datecopy.js
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-There is no way to copy/paste using a native datetime-local or
-date input. With the datecopy.js file installed, double-clicking
+When using date input types,
+there is no way to copy/paste using a native ``datetime-local`` or
+``date`` input. With the ``datecopy.js`` file installed, double-clicking
 on the input turns it into a normal text input with the ability
 to copy, paste, or manually edit the date.
 
@@ -371,18 +362,19 @@
 Revert native number inputs for Number() and Integer() (optional)
 -----------------------------------------------------------------
 
-Roundup's field() method for properties of type Number() or
-Integer() now use a native browser number input.
-
-You can use the old style text inputs by calling the field
-method with ``type="text"``. You can :ref:`follow the example
-for setting the text argument on a Date()
-property. <revert_input_to_text>` for details.
-
-Note that the Integer() type also uses ``step="1"`` by default to
+Roundup's ``field()`` method for properties of type ``Number()`` or
+``Integer()`` now use a native browser number input by default.
+
+This is configurable for *all* ``Number()`` and ``Integer()`` properties
+with the config option ``use_browser_number_input`` in section ``[web]``.
+
+You can use the old style text inputs for individual fields
+by calling the field method with ``type="text"``.
+
+Note that the ``Integer()`` type also uses ``step="1"`` by default to
 add a stepper control and try to constrain the input to
 integers. This can be overridden by passing a new step
-(e.g. ``step="50"``) to the field() method.
+(e.g. ``step="50"``) to the ``field()`` method.
 
 Change in REST response for invalid CORS requests (info)
 --------------------------------------------------------