Skip to content

Conversation

StefanRijnhart
Copy link
Member

Move functional elements of web_sheet_full_width into web_chatter_position, as it is otherwise deprecated.

Supersedes #3183 (after first having proposed the changes into that PR's branch in c4a8-odoo#17).

@OCA-git-bot
Copy link
Contributor

Hi @trisdoan,
some modules you are maintaining are being modified, check this out!

@bealdav
Copy link
Member

bealdav commented Sep 3, 2025

18.0 broken by web_systray_button_init_action module

@StefanRijnhart
Copy link
Member Author

@bealdav green in #3275

@StefanRijnhart StefanRijnhart added this to the 18.0 milestone Sep 4, 2025
@StefanRijnhart StefanRijnhart force-pushed the 18.0-imp-web_chatter_position_web_sheet_full_width_css2 branch from b15427f to 3daad80 Compare September 8, 2025 11:54
Copy link

@MohamedOsman7 MohamedOsman7 left a comment

Choose a reason for hiding this comment

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

Code & functional review LGTM

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@anajuaristi
Copy link

Hello @StefanRijnhart
Just to let you know there is a bug in web_chatter_position that is being solved in
#3282

I don't know if this is also happening in V18, but if yes, IMHO the patch should be also included here or in another PR.
My2cents.

@StefanRijnhart
Copy link
Member Author

@anajuaristi I saw that. That patch seems to break attachment rendering in our 16.0 setups for users that force the chatter below, possibly in combination with web_enterprise. We're now moving away from using this module. I might investigate during the OCA days, but you are right that this change is not compatible with that PR and we should probably not be merging this now.

@StefanRijnhart StefanRijnhart marked this pull request as draft September 12, 2025 07:59
@trisdoan
Copy link
Contributor

Hello @StefanRijnhart, fyi, that patch tries to fix a feature, which was added in #3040 for 16.0. And it's not forwarded to 18.0 yet

@StefanRijnhart
Copy link
Member Author

@trisdoan Perfect, thanks. I now see that #3282 is indeed a proposed fix for the issue we encountered in our setups, caused by #3040. In any case, this PR needs to be refactored to fit onto any port of #3040 which is likely to happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants