summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/fields/basic_fields.js
diff options
context:
space:
mode:
authorAaron Bohy <aab@odoo.com>2020-05-11 09:50:53 +0000
committerAaron Bohy <aab@odoo.com>2020-05-11 14:16:43 +0000
commit34413f706d1d91fc8f2125bf2577beab029e8538 (patch)
treeca7ee1f22507aff6bbc2dcb2bb47b2c3e011f94c /addons/web/static/src/js/fields/basic_fields.js
parent77773fddf96fafefbb24d6d075371806e3361cd5 (diff)
[FIX] web: list: multi-edition of owl fields
Before this commit, it wasn't possible to multi-edit boolean fields in list views. Actually, it didn't work for fields rendered by Owl components. It only impacted boolean fields because it was the only editable field widget that had already been converted in Owl. It didn't work because of three issues: 1) there is some sort of an hack in basic renderers: we set the attribute '__node' on the field widgets, and this attribute is used for instance by the controller, when it has to handle a multi-edition. It tries to read it from the event's target (typically the field widget). However, with owl components, '__node' was set on the FieldWrapper (wrapping the actual Field Component). 2) the original target (the Owl Component which triggered the event) was lost when the event went through the compatibility layer (for owl Component embedded in legacy widgets). 3) the multi-edition confirm dialog didn't handle Owl field components. Task 2254717 closes odoo/odoo#51044 X-original-commit: 36d23cfcdef3cea3539004ee5bb4479b859b8137 Signed-off-by: Michaƫl Mattiello <mcm-odoo@users.noreply.github.com> Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
Diffstat (limited to 'addons/web/static/src/js/fields/basic_fields.js')
0 files changed, 0 insertions, 0 deletions