[20.0][MIG] web_widget_numeric_step: Migration to 20.0 by CarlosRoca13 · Pull Request #3761 · OCA/web

CarlosRoca13 · 2026-10-28T10:09:31Z

ping @carlosdauden @sergio-teruel @carlos-lopez-tecnativa

…abled by the widget

Previous this commit the widget only works with 'dots', with this commit works using odoo parse method that support other separators.

Previous this commit, the task for auto-step can enter in a infinite loop. Now only creates a new task if no other task is running.

Currently translated at 100.0% (3 of 3 strings) Translation: web-16.0/web-16.0-web_widget_numeric_step Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_widget_numeric_step/es/

Currently translated at 100.0% (3 of 3 strings) Translation: web-16.0/web-16.0-web_widget_numeric_step Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_widget_numeric_step/it/

Mobile screens benefit most from this module's enhanced usability. However, since the events used for displaying/hiding the +/- buttons depend on mouse, at the end you'll never see these buttons on mobile screens. Thus, here's a new approach: smaller screens *always* display the buttons. Besides, inputmode is now decimal, just like upstream float fields. @moduon MT-4396

Before this patch, if a field was readonly, the user could still use the +/- buttons to alter its value. Not good! @moduon MT-4396

… layout jumping otherwise Before this patch: - On a tablet, buttons wouldn't display (big screen; can't hover). - On a PC, fields would make layout jumps while hovering. @moduon MT-4472

If you're using a tablet and click on the ➕ or ➖ buttons created by this module, the result was that the numeric input related to that button got focused. On tablets, that means that the on-screen keyboard pops up. This usually triggers a layout recalculation and becomes clunky. Besides, it's useless, because if you wanted to use the keyboard, you'd have clicked on the input by yourself, and not in one of those buttons. After this change, when using a touch screen, if you click on the +/- buttons, you won't auto-focus on the input. Thus, the keyboard won't show up. @moduon MT-4472

Before this patch, when navigating inputs hitting <kbd>TAB</kbd>, you were stopped before any numeric step input. Now, you can navigate as usual and use Odoo without a 🐁. @moduon MT-4657

Default width is too narrow for these fields in list views, which makes it uncomfortable to use in desktops. @moduon MT-4472

…ing effect The focus introduced on the 16.0 migration is causing a flickering effect that is a bit annoying and does not make complete sense, because if you click more than once the cursor is positioned at the end of the text, which makes it difficult to edit the input. The counterpart of these changes is that to edit the input using the keyboard we will have to click on the field. Although this is how the module has been operating since its inception.

…port

If we set a class in the field it will get to the widget template. TT54358

pedrobaeza · 2026-10-28T10:13:25Z

/ocabot migration web_widget_numeric_step

chienandalu · 2026-10-28T12:05:51Z

+            <field name="interval_number" position="attributes">
+                <attribute name="widget">numeric_step</attribute>
+                <attribute name="options">{'step': 2, 'min': 0, 'max': 40}</attribute>


nitpick :)

This field is an integer, so the effect on it is that it's showed as float.

Maybe add a roadmap entry indicating this known issue or even probable future support.

In the other hand, you can use some of the paper format margin fields for the demo data, which are real floats and are available in web

carlos-lopez-tecnativa · 2026-10-28T18:48:38Z

+number, so you can use the options `min`, `max`, `step`, `placeholder`.
+
+Demo available at Settings \> Users & Companies \> Users \> \*Select
+One\* \> See 'Credit Limit' field


This README is outdated: this field has never belonged to ir.cron. Please update it.

carlos-lopez-tecnativa · 2026-10-28T18:52:14Z

+    updateField(val) {
+        return this.props.record.update({[this.props.name]: val});
+    }
+    _doStep(mode) {


I think we shouldn't update the field in the view if it's read-only, because when the record is saved, the field is restored to its original value, which is a bad experience for the user. Could you handle this, or add it to the ROADMAP?

2026-10-28.13-49-13.mp4

OCA-git-bot added mod:web_widget_numeric_step Module web_widget_numeric_step series:20.0 labels Oct 28, 2026

quentinDupont and others added 28 commits October 28, 2026 11:10

[ADD] Widget Numeric step

205d3de

[IMP] web_widget_numeric_step: Better CSS and supports mobile layouts

817056b

[FIX] web_widget_numeric_step: Float Precision

7460a31

[FIX] web_widget_numeric_step: Fix _onChange input fields methods dis…

a2a4858

…abled by the widget

[IMP] web_widget_numeric_step: Event handler

6ad20a2

[FIX] web_widget_numeric_step: Change number parse method

82304b0

Previous this commit the widget only works with 'dots', with this commit works using odoo parse method that support other separators.

[FIX] web_widget_numeri_step: Change click interval

821c419

Previous this commit, the task for auto-step can enter in a infinite loop. Now only creates a new task if no other task is running.

Added translation using Weblate (Spanish)

da25f01

[IMP] web_widget_numeric_step: better visualization in list view cells

8387144

[FIX] web_widget_numeric_step: Only modify widget parent

541ed81

[IMP] web_widget_numeric_step: black, isort, prettier

2984eea

[MIG] web_widget_numeric_step: Migration to v13

f9a6166

Added translation using Weblate (Italian)

534bafe

[IMP] web_widget_numeric_step: Add auto_select option

39c4c83

[IMP] web_widget_numeric_step: isort, black, prettier.

afcc050

[MIG] Migrate module web_widget_numeric_step to v14.

6307778

Added translation using Weblate (German)

d2f5355

[MIG] web_widget_numeric_step: Migration to 15.0

3ffccaf

[IMP] web_widget_numeric_step: pre-commit stuff

8de6c9e

[MIG] web_widget_numeric_step: Migration to 16.0

653efae

Translated using Weblate (Spanish)

1423bc7

Currently translated at 100.0% (3 of 3 strings) Translation: web-16.0/web-16.0-web_widget_numeric_step Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_widget_numeric_step/es/

Translated using Weblate (Italian)

5ac9b79

Currently translated at 100.0% (3 of 3 strings) Translation: web-16.0/web-16.0-web_widget_numeric_step Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_widget_numeric_step/it/

[FIX] web_widget_numeric_step: disable buttons on readonly fields

23efcc0

Before this patch, if a field was readonly, the user could still use the +/- buttons to alter its value. Not good! @moduon MT-4396

[FIX] web_widget_numeric_step: always display on touch screens; avoid…

ce4620b

… layout jumping otherwise Before this patch: - On a tablet, buttons wouldn't display (big screen; can't hover). - On a PC, fields would make layout jumps while hovering. @moduon MT-4472

[FIX] web_widget_numeric_step: restore tab navigation

e66917d

Before this patch, when navigating inputs hitting <kbd>TAB</kbd>, you were stopped before any numeric step input. Now, you can navigate as usual and use Odoo without a 🐁. @moduon MT-4657

[FIX] web_widget_numeric_step: list view column min width

65a8932

Default width is too narrow for these fields in list views, which makes it uncomfortable to use in desktops. @moduon MT-4472

achulii and others added 9 commits October 28, 2026 11:10

[IMP] web_widget_numeric_step: pre-commit auto fixes

9d368fc

[MIG] web_widget_numeric_step: Migration to 17.0

9a1eb13

[IMP] web_widget_numeric_step: Add demo data to test the module

8e2651c

[MIG] web_widget_numeric_step: Migration to 18.0

6cc9307

[FIX] web_widget_numeric_step: remove odoo-module tag and fix sort-im…

44255d2

…port

[IMP] web_widget_numeric_step: be able to add classes

32c1ff2

If we set a class in the field it will get to the widget template. TT54358

[MIG] web_widget_numeric_step: Migration to 19.0

4e9b944

[IMP] web_widget_numeric_step: pre-commit auto fixes

6b280f4

CarlosRoca13 force-pushed the 20.0-mig-web_widget_numeric_step branch from d4e4839 to d9b8d3c Compare October 28, 2026 10:10

OCA-git-bot added this to the 20.0 milestone Oct 28, 2026

OCA-git-bot mentioned this pull request Oct 28, 2026

Migration to version 20.0 #3688

Open

3 of 36 tasks

[MIG] web_widget_numeric_step: Migration to 20.0

9b1ec51

CarlosRoca13 force-pushed the 20.0-mig-web_widget_numeric_step branch from d9b8d3c to 9b1ec51 Compare October 28, 2026 10:21

carlosdauden approved these changes Oct 28, 2026

View reviewed changes

chienandalu reviewed Oct 28, 2026

View reviewed changes

carlos-lopez-tecnativa suggested changes Oct 28, 2026

View reviewed changes

Navigation Menu

Repository navigation

[20.0][MIG] web_widget_numeric_step: Migration to 20.0 - #3761

[20.0][MIG] web_widget_numeric_step: Migration to 20.0#3761
CarlosRoca13 wants to merge 38 commits into
OCA:20.0from
Tecnativa:20.0-mig-web_widget_numeric_step

CarlosRoca13 commented Oct 28, 2026

Uh oh!

pedrobaeza commented Oct 28, 2026

Uh oh!

chienandalu Oct 28, 2026

Uh oh!

carlos-lopez-tecnativa Oct 28, 2026

Uh oh!

carlos-lopez-tecnativa Oct 28, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants

Conversation

CarlosRoca13 commented Oct 28, 2026

Uh oh!

pedrobaeza commented Oct 28, 2026

Uh oh!

chienandalu Oct 28, 2026

Choose a reason for hiding this comment

Uh oh!

carlos-lopez-tecnativa Oct 28, 2026

Choose a reason for hiding this comment

Uh oh!

carlos-lopez-tecnativa Oct 28, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants