Tuesday, March 4, 2025
5 changes · saas-18.1
Resolved issues and error corrections
Fixed an issue in the mail testing helper that caused automated checks for compact chat notifications to fail even though the feature worked correctly for users. This improves test reliability and helps prevent false alarms in the development pipeline.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/199828 PR above added a new test that resulted in frequent runbot failures: ``` Failed assertions: 1. [toBe] Failed to find 1 of…
Follow-up of https://github.com/odoo/odoo/pull/199828 PR above added a new test that resulted in frequent runbot failures: ``` Failed assertions: 1. [toBe] Failed to find 1 of ".o-mail-ChatHub-compact" with text "1" (Timeout of 3 seconds). Found 0 instead. > Expected: true > Received: false 2. [errors] 1 unverified error(s) Error during test: Failed to find 1 of ".o-mail-ChatHub-compact" with text "1" (Timeout of 3 seconds). Found 0 instead. ``` This happens because the test had a chat window open, enabled the compact mode of chat hub, then posts a message and assert there's a counter on the chathub compact button. Everything works fine when a human do these interactions. However the test failed because there was no counter. This comes from chat window modeling that was thinking the composer was still focused, therefore it was marking the conversation as read, leading to consuming the "1" counter. Composer was kept in "focused" state because when programmatically simulating a `click`, the detection of loss of focus is made with a `focusout` event that is triggered normally on the previously focused element. In HOOT, the `@mail` click test helper was not triggering `focusout` on the previous element. This commit fixes the issue by triggering `"focusout"` on the previously active element in the `click` helper of `@mail` when the previous element is not the same as the next. runbot-159692 https://runbot.odoo.com/runbot/build/76027155
This update rolls back a recent change to QR code downloads in the self-ordering point of sale flow because it was not compatible with the server environment. This keeps the stable version reliable while the deployment issue is addressed separately.
Original PR description
This reverts commit 3d447856467e7ad72f0a89c71b643940b8ea5321. This was incompatible with the lxml version we have on our server. Revert for a quick fix until we have corrected the deployment (which will be slower) Task-id 4575936 is a new feature that should not have targeted a stable version
Expanding the call participant avatars in the Discuss sidebar no longer causes a small visual jump. This makes the call interface feel steadier and more polished for users.
Original PR description
In the Discuss sidebar, an avatar stack displays call participants and can be expanded for more details. Expanding the stack caused a slight shift due to the stack using padding for a background-colored border, while the expanded list did not. This PR fixes the issue by: - Removing margin from the stack container for better flexibility (customizable via `containerClass`). - Applying the same padding to the expanded list to maintain alignment. | Before | After | | ------------- | ------------- | |  | |
Call diagnostic logs now include the Odoo version, making it easier for support teams to understand the environment when investigating call issues. The generated log filename date was also corrected, helping teams identify and organize logs more reliably.
Original PR description
This commit also fixes the filename date log example: 
This fixes an issue where Windows-connected printers could hit an error when the system tried to reprint pairing status information. The status reprint is now limited to Linux environments, keeping printer setup behavior stable across supported systems.
Original PR description
The PR #198791 introduced a reprinting of the pairing codes on the connected printers. However connected_by_usb variable isn't present in PrinterDriver_W which resulted in an error. This PR only reprints the status on the connected printer if we are on a Linux system