diff options
| author | Christophe Simonis <chs@odoo.com> | 2018-07-31 19:36:30 +0200 |
|---|---|---|
| committer | Christophe Simonis <chs@odoo.com> | 2018-07-31 19:36:30 +0200 |
| commit | 8c81eaabe6b451b112f6af5b2bb06afe9ed91839 (patch) | |
| tree | 3dbfd10960e2077d6ae9025bd3c6d0b7f382772a /addons/web/static/src/js/fields/basic_fields.js | |
| parent | 96de6756ab9794ad30da7965ccb723e3c44cd343 (diff) | |
Revert "[FIX] models: make `onchange` return a smaller diff"
This reverts commit 2054b5928574affbb7efcd8a9ab146ee4fa34938 which
already has been fixed multiple times [0].
However this change does not correctly handle successive onchange calls on
ony2many fields which alter existing rows.
i.e., in saas~11.4, an onchange has been added on move lines [1] in
order to create and/or update lines containing taxes amounts.
However, with diff-only onchange, a second call to onchange will discard
changes made by a first one as nothing change between the 2 calls.
Scenario: On an existing account.move, add a new credit line with a tax set.
The first onchange will update the tax line with new amount. Add a
second line (with debit amount balanced). The onchange will not change
the tax line, resulting as it value being reset to initial value. As a
result, the move is not balanced and cannot be saved.
[0] cd2ccc4110274e23607521c18309f07cca68476a, 5e58ac16c3cae2d5c45e7c9f746ed810b835a65d, 07023137cd17d8917673fd6ba7809b2870bd8cc0
[1] d49ab568a2cc5231ac12267a9e74eaf16ca45f9e
Diffstat (limited to 'addons/web/static/src/js/fields/basic_fields.js')
0 files changed, 0 insertions, 0 deletions
