Skip to content

Commit e68f652

Browse files
committed
docs: issue2551398 document enabling native browser number/integer types
The original default was to have them enabled. Due to issues with locale (e.g. decimal thousands separator vs comma seperator) this is disabled by default. See issue for details.
1 parent c05bf68 commit e68f652

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

doc/upgrading.txt

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -362,11 +362,11 @@ There is no support for activating text mode using the
362362
keyboard. Tablet/touch support is mixed. Chrome supports
363363
double-tap to activate text mode input. Firefox does not.
364364

365-
Revert native number inputs for Number() and Integer() (optional)
365+
Enable native number inputs for Number() and Integer() (optional)
366366
-----------------------------------------------------------------
367367

368368
Roundup's ``field()`` method for properties of type ``Number()`` or
369-
``Integer()`` now use a native browser number input by default.
369+
``Integer()`` can use a native browser number input by default.
370370

371371
This is configurable for *all* ``Number()`` and ``Integer()`` properties
372372
with the config option ``use_browser_number_input`` in section ``[web]``.
@@ -379,6 +379,8 @@ add a stepper control and try to constrain the input to
379379
integers. This can be overridden by passing a new step
380380
(e.g. ``step="50"``) to the ``field()`` method.
381381

382+
This is an experiment and maybe changed based on feedback.
383+
382384
Change in REST response for invalid CORS requests (info)
383385
--------------------------------------------------------
384386

0 commit comments

Comments
 (0)