diff options
| author | len-odoo <len@odoo.com> | 2018-04-10 09:05:55 +0200 |
|---|---|---|
| committer | len-odoo <35492570+len-odoo@users.noreply.github.com> | 2018-04-10 09:32:05 +0200 |
| commit | eca99f1f12174cc59e7ff93c40a3aedc2d422049 (patch) | |
| tree | 514efd5a58b9dcfaef37be447f7abb5a4c5de5fb /addons/web/static/lib/bootstrap-datetimepicker/src/js/bootstrap-datetimepicker.js | |
| parent | 6ee5b6fd6fe62db0c3bf8e6d5d7fb8052724589a (diff) | |
[FIX] point_of_sale: fix quantity rounding
When the user set a decimal accuracy on the product quantity, the point_of_sale
(POS) frontend would display the correct rounding of the quantity according to
both the decimal accuracy and the rounding set on the unit of measure.
However the quantity used to compute the price was only using the rouding on the
unit of measure. This led to an inconsistency in what is encoded in the backend,
and thus made it impossible to close the session as the price paid by customers
did not match what is encoded.
The problem comes from the fact that there is a variable this.quantity and
another one to display this.quantityStr. Unsurprisingly, this.quantityStr
was not computed directly from this.quantity, leading to the inconsistency.
opw 1826092
Diffstat (limited to 'addons/web/static/lib/bootstrap-datetimepicker/src/js/bootstrap-datetimepicker.js')
0 files changed, 0 insertions, 0 deletions
