Monday, March 3, 2025
4 changes · saas-18.1
Resolved issues and error corrections
The mail app now plays a shorter, less intrusive sound when new messages arrive, especially helpful during busy conversations. It also correctly respects the user's message sound setting, so turning sounds off now works as expected in Discuss conversations.
Original PR description
This PR fixes 2 issues: 1. new message sound effect had too long decay, this PR reduces it significantly 2. "message sound" toggle settings to enable or disable "new message" sound effect was not working properly. Before https://github.com/user-attachments/assets/0d4482ee-ca25-4312-b4e7-85cea4d1f085 After https://github.com/user-attachments/assets/089d5546-8aa6-4145-8105-88695bd6f2b4
Users can now intentionally open chat windows even when the chat hub is in compact mode. This keeps the quieter compact experience while still allowing access to conversations through tools like the command palette or messaging menu.
Original PR description
The chat hub's compact mode hides all chat windows to prevent disturbances, mainly from automatic actions. However, users should still be able to open chats explicitly (e.g., via the command palette or messaging menu). This PR allows user-initiated chats to open even in compact mode, balancing distraction-free usage with accessibility.
Users on mobile devices such as iPads can now add emoji reactions in Discuss without the page crashing. The fix ensures the mobile-friendly emoji picker is used consistently, improving reliability for mobile users.
Original PR description
Before this commit, when using an ipad in portrait mode, clicking on message action "add a reaction" resulted to the following crash: ``` Uncaught Promise > Cannot read properties of undefined…
Before this commit, when using an ipad in portrait mode, clicking on message action "add a reaction" resulted to the following crash: ``` Uncaught Promise > Cannot read properties of undefined (reading 'getRootNode') ``` This happens because in mobile, the message actions are displayed with mobile action menu. Clicking on "Add a reaction" opens the emoji picker, which should open the mobile version of the emoji picker. However, the inner-code of emoji picker was attempting to use the desktop emoji picker, due to relying on screen size rather than `isMobileOS()`. The desktop mode of emoji picker needs a anchor target, which is the quick message action "add a reaction" in desktop. In mobile this doesn't exist, thus the anchor was `undefined`, and inner-code of popover crashes when the anchor el is undefined. This commit fixes the issue by using the mobile emoji picker mode using `isMobileOS()` rather than `ui.isSmall`. This makes showing of mobile emoji picker consistent for all mobile devices, which matches the expected UX/UI in Discuss. opw-4606671
This fix prevents visitors from sending multiple answers while the chatbot is still processing their previous response. It helps avoid duplicate messages and inconsistent chat flows, especially on slow connections.
Original PR description
Before this PR, the composer was not always blocked after the user answered a question. This can lead to multiple answers being posted and inconsistent state. Steps to reproduce: - Create a chat bot with a free input step. - Open a live chat with this chat bot. - Throttle your network to 3G speed. - You can send many messages during the delay. This PR ensures the composer is disabled as soon as the user answers the bot until the next step is ready. part of task-4607689 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr