Skip to content

[19.0][MIG] web_chatter_position: Migration to 19.0#3325

Open
BhaveshHeliconia wants to merge 21 commits intoOCA:19.0from
HeliconiaIO:19.0-mig-web_chatter_position
Open

[19.0][MIG] web_chatter_position: Migration to 19.0#3325
BhaveshHeliconia wants to merge 21 commits intoOCA:19.0from
HeliconiaIO:19.0-mig-web_chatter_position

Conversation

@BhaveshHeliconia
Copy link
Copy Markdown
Contributor

No description provided.

@BhaveshHeliconia BhaveshHeliconia mentioned this pull request Oct 17, 2025
44 tasks
Copy link
Copy Markdown

@DucTruongKomit DucTruongKomit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested, no application error and any wrong so far.
Could you help to solve pre-commit and squash commit, please? @BhaveshHeliconia

@quoc-pn
Copy link
Copy Markdown
Member

quoc-pn commented Jan 20, 2026

@BhaveshHeliconia I can not find the runboat instance to test, could you please help check? Thank you!

@BhaveshHeliconia BhaveshHeliconia force-pushed the 19.0-mig-web_chatter_position branch from 37130d2 to 7b41597 Compare January 20, 2026 08:11
@BhaveshHeliconia
Copy link
Copy Markdown
Contributor Author

@quoc-pn : The Runboat instance is now up and running. You can test it now. Thanks!

@quoc-pn
Copy link
Copy Markdown
Member

quoc-pn commented Jan 20, 2026

Hi @BhaveshHeliconia

The chatter width in “Sided” position is too large and reduces usable space when displaying large content.

I expect the width to be the same as the "Responsive" position.

image

@BhaveshHeliconia BhaveshHeliconia force-pushed the 19.0-mig-web_chatter_position branch 2 times, most recently from 4614577 to cc5e080 Compare January 20, 2026 09:28
@BhaveshHeliconia
Copy link
Copy Markdown
Contributor Author

@quoc-pn : Good catch. I’ve fixed the issue and aligned the width with the “Responsive” position. Please check again. Thanks!

Copy link
Copy Markdown
Member

@quoc-pn quoc-pn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functional tested, LGTM!

@quoc-pn
Copy link
Copy Markdown
Member

quoc-pn commented Jan 20, 2026

@BhaveshHeliconia BhaveshHeliconia force-pushed the 19.0-mig-web_chatter_position branch from cc5e080 to b921fec Compare January 20, 2026 10:31
@BhaveshHeliconia
Copy link
Copy Markdown
Contributor Author

"license": "LGPL-3",
"category": "Extra Tools",
"depends": ["web", "mail"],
"depends": ["web", "mail", "hr"],
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it "hr" mandatory to have this feature?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you remove it? I don't think users want an useless module for this feature

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I've removed it.

@quoc-pn
Copy link
Copy Markdown
Member

quoc-pn commented Feb 9, 2026

@BhaveshHeliconia
There is improvement in v18 (#3183). Please help include those changes in this PR. Thank you!

MohamedOsman7 and others added 3 commits February 11, 2026 12:14
@BhaveshHeliconia BhaveshHeliconia force-pushed the 19.0-mig-web_chatter_position branch from b921fec to 049dba1 Compare February 11, 2026 06:47
Comment on lines -27 to -30
const chatterContainerXml = chatterContainerHookXml.querySelector(
"t[t-component='__comp__.mailComponents.Chatter']"
);
// Const chatterParent = chatterContainerXml.parentNode;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you reconsider these changes after applying the changes for branch 18.0?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to remove this code after applying the change from branch 18.0?

Comment on lines -43 to -53
} else if (odoo.web_chatter_position === "sided") {
setAttributes(chatterContainerXml, {
isInFormSheetBg: `__comp__.uiService.size < ${SIZES.XXL}`,
isChatterAside: `__comp__.uiService.size >= ${SIZES.XXL}`,
});
setAttributes(chatterContainerHookXml, {
class: "o-mail-ChatterContainer o-mail-Form-chatter o-aside w-print-100",
});
// For "bottom", we keep the chatter in the form sheet
// (the one used for the attachment viewer case)
// If it's not there, we create it.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you reconsider these changes after applying the changes for branch 18.0?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to remove this code after applying the change from branch 18.0?

Comment on lines -78 to -85
const sheetBgChatterContainerXml =
sheetBgChatterContainerHookXml.querySelector(
"t[t-component='__comp__.mailComponents.Chatter']"
);

setAttributes(sheetBgChatterContainerXml, {
isInFormSheetBg: "true",
});
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you reconsider these changes after applying the changes for branch 18.0?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to remove this code after applying the change from branch 18.0?

@quoc-pn
Copy link
Copy Markdown
Member

quoc-pn commented Feb 11, 2026

@BhaveshHeliconia
There are some commit made by Bots, please follow steps in the link below to clear them. Thank you!
https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-19.0#:~:text=Check%20https%3A//github.com/OCA/maintainer%2Dtools/wiki/Merge%2Dcommits%2Din%2Dpull%2Drequests%20for%20a%20procedure%20for%20reducing%20commits%20from%20%22OCA%20Transbot...%22.

@quoc-pn Done. Thanks!

I think you need to redo this process.

@landlogicit
Copy link
Copy Markdown

Thanks for module web_chatter_position migrate to 19.x, good job

@BhaveshHeliconia
Copy link
Copy Markdown
Contributor Author

BhaveshHeliconia commented Feb 20, 2026

@BhaveshHeliconia
There are some commit made by Bots, please follow steps in the link below to clear them. Thank you!
https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-19.0#:~:text=Check%20https%3A//github.com/OCA/maintainer%2Dtools/wiki/Merge%2Dcommits%2Din%2Dpull%2Drequests%20for%20a%20procedure%20for%20reducing%20commits%20from%20%22OCA%20Transbot...%22.

@quoc-pn Done. Thanks!

I think you need to redo this process.

I’ve already done the process. There are no bot commits anymore.

Copy link
Copy Markdown
Member

@quoc-pn quoc-pn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please help resolve all reviews in the PR, thank you!

@BhaveshHeliconia
Copy link
Copy Markdown
Contributor Author

@quoc-pn The code was removed because Odoo 19 (following the architecture introduced in v18) now natively handles chatter positioning logic.

Specifically, the mail module's native FormCompiler patch already identifies the Chatter component and dynamically sets the isInFormSheetBg and isChatterAside props based on the mailLayout() state.

Since super.compile() is called first, these attributes are already correctly configured by Odoo. Manually reapplying them here is not only redundant but could conflict with Odoo 19's native responsiveness, especially when handling the 'Combo' layout or attachment previews. Removing this logic ensures a cleaner integration and prevents potential UI bugs during layout transitions

@BhaveshHeliconia BhaveshHeliconia force-pushed the 19.0-mig-web_chatter_position branch from 049dba1 to 13ac70a Compare April 10, 2026 07:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.