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.
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
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:
- 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
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
OCA-git-bot
Duy (Đỗ Anh)
Weblate
oca-ci
Carlos Roca
achulii
Jairo Llopis
mymage
Ivorra78
dsolanki
Thanakrit Pintana
Corneliuus
helly
fshah
Alexandre D. Díaz
Alessandro Fiorino
Ernesto Tejeda
claudiagn
Sergio Teruel
Quentin Dupont