Daily updates from Odoo
Tuesday, April 15, 2025
7 changes
Resolved issues and error corrections
The portal rating comment box now clears saved draft content when a comment is posted or cancelled. It also prevents crashes caused by users saving the same comment twice, improving reliability for portal discussions.
Original PR description
Fix some issues related to the comment composer in portal chatter. task-4715576
Chat messages no longer briefly change width while they are being sent. This removes a small visual flicker, making conversations feel more stable and polished for users.
Original PR description
Before this commit, when posting a message in chat window, the new message being posted had its size flicker momentarily. This happens because when posting a new message, the message list contains a temporary message with the content momentarily and soon replaced by the genuine message from server data. The genuine message shows quick actions like "Add a reaction", which the temporary message has not. Since these quick actions take some horizontal place, the temporary message was bigger on width than an actual message, which results to this flickering when the message takes more than 1 line. This commit fixes the issue by allocating some space when a message has less (or no) available quick actions, so that their size matches with genuine message that have quick actions. Before / After  
This fix prevents the website menu from crashing when an expected mobile mega menu element is missing. It helps keep edited or older website pages working reliably instead of breaking the visitor experience.
Original PR description
This commit ensures that the mega menu toggles are only accessed if they exist in the DOM. This prevents a crash when the mega menu toggles are not present. The PR that added this code can be found here: 5be1280 This first appeared in an 18.1 ticket where a customer had a view created by the web editor that was missing the expected mega menu mobile version. This view had been edited and not upgraded properly, leading to a case where the mobile mega menu toggle element was not present. opw-4670537
This fix prevents accidental selection of a hovered @mention suggestion when users press Enter in Discuss or chatter. Keyboard selection now stays predictable, reducing mistakes when quickly mentioning someone.
Original PR description
Before this commit, when typing a `@mention` in a discuss or chatter composer, pressing ENTER was selecting the item hovered on cursor rather than the 1st item. This happens because by default the…
Before this commit, when typing a `@mention` in a discuss or chatter composer, pressing ENTER was selecting the item hovered on cursor rather than the 1st item. This happens because by default the active suggestion is the 1st one in list, and keyboard navigation changes the active item. However mouse-enter was also selecting the active item. When the suggestion opens initially, if the cursor happens to be on the list, it is being considered as a `mouseenter` this it sets the active suggestion. This is a problem because this is very prone to mistakes. The feature to set the active item for following keyboard navigation is very niche and not necessarily much intuitive than just typing more specific search and rely solely on keyboard navigation or mouse-click. One solution could be to only take mouse hover into account if it moves after the suggestion list is rendered, but this is still prone to mistakes like people typing on a laptop keyboard while accidentally touching the trackpad. This commit fixes the issue by making mouse-hover on suggestion list only trigger the visual style but it doesn't change the internal state of the active suggestion. Task-4724275 Cursor in middle of suggestion list, quickly `@` + `ENTER` Before (selects suggestion in middle of list, at cursor position)  After (selects 1st suggestion in list, independently of cursor position in list) 
This update documents why certain hidden fields are still needed in Swiss localization screens and removes hidden fields that are no longer necessary. It helps keep the module compliant with Odoo view guidelines without changing day-to-day user workflows.
Original PR description
Before this commit, several invisible fields were present in the views in `l10n_ch`, whereas after https://github.com/odoo/odoo/pull/162009 these fields need to be either justified or removed. This commit adds comment for the fields that are needed, and removes the unnecessary ones. opw-4629332 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Guided tours now wait correctly when dropdown options are still loading, preventing the flow from jumping back to the previous input step. This makes automated walkthroughs and onboarding checks more reliable for users and testers.
Original PR description
Before this commit, if the tour steps was "edit input" then "click second element dropdown", the tour was stuck and was backwarding to the "edit input" because during a moment the dropdown had only one element (the loading). Now, the loading will be taken in account to wait for the next mutation observer for the case of a dropdown TASK-ID: 4623449 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Sales app’s sample quotation button now points to a valid PDF link. This prevents users from seeing a blank 404 error page when exploring the feature without demo data installed.
Original PR description
Currently, a 404 error is occurring when the user clicks on the Check the sample button. <b>Steps to reproduce this issue:</b> 1) Install sales without demo data 2) Click on the `Check a sample. Its clean!` button <b>Issue:- </b> A 404 error occurs with a blank page <b>Cause:-</b> This issue is occurring because the link to open the sample quotation was changed in the Odoo documentation. <b>Solution:-</b> Give a valid link to open the sample quotation pdf opw-4708039