odoo/odoo#195183
Created by fw-bot
Merged
at 649fa1af6b3e4347731684a48e18700c02fb071f
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/template: Contact runbot team on discord for help.
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- label
- odoo-dev:saas-17.4-17.0-mail-render-messageActions-with-callComponent-2jhf-fw
- head
- 8de46fa5c726a79eb0bb0712bf70795af6d11b99
- merged
- 9 months ago by Discuss, Alexandre Kühn (aku)
odoo/odoo | |
---|---|
17.0 | #194643 |
saas-17.2 | #194751 |
saas-17.4 | #195183 |
18.0 | #195185 |
saas-18.1 | #195189 |
saas-18.2 | |
saas-18.3 | |
saas-18.4 | |
19.0 | |
master | #195205 |
[FW][17.0][FIX] mail: Render message actions correctly with callComponent
Description of the issue/feature this PR addresses:
When a custom module (e.g., OCA/social#1536) adds a new message action using callComponent
, it is not invoked in certain scenarios.
Current behavior before PR:
Odoo only invokes callComponent
for quick actions
(2 or 3 actions). For remaining actions rendered as DropdownItem
, the callComponent
is not invoked.
Desired behavior after PR is merged:
This commit ensures consistent rendering behavior, invoking the callComponent
for all actions, whether quick actions or dropdown items.
Complementary to: #131426
@phenix-factory @alexkuhn coud you please review this?
CC @pedrobaeza @chienandalu
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr