diff options
| author | Denis Ledoux <dle@odoo.com> | 2018-10-18 15:33:17 +0000 |
|---|---|---|
| committer | Denis Ledoux <dle@odoo.com> | 2018-10-18 15:37:42 +0000 |
| commit | b7937ab6b7c14131ac6dde9a3b35eaa2b449f932 (patch) | |
| tree | 9adf7a324f71726b190c0ec33f88c134eb3d49db /addons/web/static/src | |
| parent | 2c0a76fc7a57db8245c4ac9fbd1a71b80114ce87 (diff) | |
[FIX] web: re-introduce on_change="0" to prevent onchanges for customization
In 10.0, adding on_change="0" allowed to prevent
default onchanges to occur for the field on which was added this attribute.
In 11.0, the rev. eaa66d11568b415b8d6b4c7a17a058b5ec1df4a6
added a regression by removing this possibility.
It was an oversight, it was not an expected change
in the web client.
In 10.0, it's this line which bring this possibility:
https://github.com/odoo/odoo/commit/e8a00bc50da435d3859118ca127d20a2eb9a0cab#diff-ff0e90fb0eb4418a7f66e618e4b51323R444
opw-1883366
closes odoo/odoo#27952
Diffstat (limited to 'addons/web/static/src')
| -rw-r--r-- | addons/web/static/src/js/services/data_manager.js | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/addons/web/static/src/js/services/data_manager.js b/addons/web/static/src/js/services/data_manager.js index 9b11f3a54a7..bdfe2a7dbaf 100644 --- a/addons/web/static/src/js/services/data_manager.js +++ b/addons/web/static/src/js/services/data_manager.js @@ -273,7 +273,7 @@ return core.Class.extend({ attrs.options = attrs.options ? pyeval.py_eval(attrs.options) : {}; } - if (attrs.on_change && !field.onChange) { + if (attrs.on_change && attrs.on_change !== "0" && !field.onChange) { field.onChange = "1"; } |