Tuesday, May 20, 2025
6 changes · saas-18.2
Resolved issues and error corrections
Product ecommerce descriptions now block editing tools that do not work on the storefront, such as toggle lists. This prevents shoppers from seeing broken or confusing product description content and helps editors create content that displays correctly online.
Original PR description
Scenario: - go in backend of a product > "Sales" tab > "Ecommerce Description" - type "/" and select "Toggle List" style - enter a shown line, and a toggle-able line - go to the website view of this product Result: the "Toggle List" widget code is not working and we see both line without the toggling possible. Issue: the "Toggle List" feature was meant to only be added to knowledge and backend field that are not mailing or website and the toggle list is already disabled in frontend website. Fix: in the backend, disable embedded_components for the given field. opw-4793768 __PR note:__ a similar fix was done in e9b372f04726e800f9f7427aac697f12a2e2a01f and 289517e7ca38dcd7e84c4fc4bc6118429f2a25d0
This fix improves the reliability of automated checks around text selection in the HTML editor by waiting longer for selection updates to complete. It helps prevent intermittent editor-related failures, supporting a more stable editing experience for users.
Original PR description
It looks like in some cases awaiting for a microtask tick is not enough for the selectionchange handlers to be called. This commit waits for a full tick instead. This is a stronger version of the original fix at https://github.com/odoo/odoo/pull/210022.
This fix makes automated editor tests wait more reliably before checking text selection behavior. It helps prevent occasional false test failures, supporting smoother development and release validation without changing customer-facing features.
Original PR description
It looks like in some cases awaiting for a microtask tick is not enough for the selectionchange handlers to be called. This commit waits for a full tick instead. This is a stronger version of the original fix at https://github.com/odoo/odoo/pull/210022.
Fleet managers can now change the planned future driver for multiple vehicles at once. This removes an error that previously blocked bulk updates and makes vehicle administration faster and more reliable.
Original PR description
Before this commit, it was not possible to update in batch the future driver of many vehicle because a check made during the update expects there is only one vehicle to update. This commit fixes the issue to be able to alter the future driver on many vehicle at the same time.
This fixes the placement of message action buttons on mobile screens in regular conversations while preserving the intended card-style layout in mailboxes like the Inbox. Users get a consistent and usable mobile messaging experience without disrupting the mailbox view.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/210304 PR above improve message actions placement in mobile in card layout, such as in Inbox. However it makes a regression in placement of other message actions. This commit fixes the issue by keeping the card visual of message actions as the fix for card layout and same visual as before the fix for non-card messages. Before / After in mailboxes (unchanged)   Before / After in conversation (fixed)  
A typo was corrected so the planning calendar properly detects when a schedule item is being dragged. This prevents the split action from running at the wrong time, making schedule adjustments more reliable for users.
Original PR description
Before this commit, the code checks if `this.connectorDragState.draging` if truly before using the split tool because we don't want to execute that if the user is currently dragging a planning slot. The problem is `draging` attribute does not exist in `connectorDragState`, it should be `dragging` instead. This commit fixes the typo to correctly check if the slot is dragging before doing the split tool or not.